Typically, they are used to put each application’s URLs into their own namespace. This prevents the reverse() Django function and the {% url %} template function from returning the wrong URL because the URL-pattern name happened to match in another app. What I have in my project-level urls.py file is the following: from django.conf.urls.defaults import … Read more
Here’s what I do. In <mylibrary.h>: namespace myproject { namespace mylibrary { namespace impl { using namespace otherlibrary; using namespace boost; using namespace std; using namespace whatever::floats::your::boat; class myclass; class myotherclass; }; using impl::myclass; using impl::myotherclass; }; }; In the source: #include <mylibrary.h> using namespace myproject::mylibrary; //clean!
Simply “moving” Devise to the admin namespace is wrong. Devise uses controllers like Devise::SessionsController and that cannot be “moved”. I usually create my own controllers and inherit them from Devise: class Admin::SessionsController < ::Devise::SessionsController layout “admin” # the rest is inherited, so it should work end And configure this in config/routes.rb: devise_for :admins, :controllers => … Read more
tl;dr: Do not choose the past. Choose the future: Modules. In early drafts of the ES6 modules specification, there was an inline modules notion, which then has been eliminated in September 2013. However, this notion was already implemented by the TypeScript team, in 2012, with the first beta versions of the language: it was internal … Read more
Kubernetes 1.13 and earlier They cannot be shared, because they cannot be accessed from a pods outside of its namespace. Names of resources need to be unique within a namespace, but not across namespaces. Workaround it is to copy it over. Copy secrets between namespaces kubectl get secret <secret-name> –namespace=<source-namespace> –export -o yaml \ | kubectl apply –namespace=<destination-namespace> … Read more
Well, according to the documentation, “The System.Diagnostics namespace provides classes that allow you to interact with system processes, event logs, and performance counters.” So I guess by definition it fits. 🙂 But yes, it does seem a bit like an overloading of terms by putting it next to things a bit more obviously diagnostics-related (tracing, … Read more
If the function is only used in one source file, it makes perfect sense to define it there. If nobody else is using it, it doesn’t belong in the header. As you say, it reduces dependencies and can potentially save some recompiles.
From the SGI docs (here): [1] Strictly speaking, iter_swap is redundant. It exists only for technical reasons: in some circumstances, some compilers have difficulty performing the type deduction required to interpret swap(*a, *b).