René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"in-ns special form oddities","articleBody":"1) Imagine you are writing a test that operates on namespaces, but you don't want it to conflict with other tests that operate on namespaces, so you give the namespace a long name nested \"within\" your test namespace, like pixie.tests.test-stdlib.foo. Then, because you want to refer to that namespace several times within the test, and you don't want to write it out each time, you assign it to a local, like this.\n\n```\n(let [test-ns :pixie.tests.test-stdlib.foo]\n  (in-ns test-ns)\n  (def y 3)\n  etc. etc.)\n```\n\nExcept the test fails. You expected that y would be created within pixie.tests.test-stdlib.foo, but instead it's created within namespace \"test-ns\". That's because in-ns is a special form at compile time, and it sets the compile-time namespace to \"test-ns\". Then it becomes a function at run time, and it sets the run-time namespace to pixie.tests.test-stdlib.foo, as you would see if you examined `*ns*`. I think that behavior is confusing.\n\n2) In the same vein, in-ns affects the environment even if never executed.\n\n```\nuser =\u003e (defn g [] (in-ns :pixie.tests.test-stdlib))\n\u003cVar user/g\u003e\npixie.tests.test-stdlib =\u003e \n```\n\nSo in this case, even though g was only compiled but not executed, it affected the current namespace. Similar stuff happens with `if` statements -- if you have an if statement in which one branch sets the namespace to :foo and another to :bar, all vars resolved after that will be resolved in the namespace of the second branch, etc..  The only thing that matters is the order in which the compiler encounters in-ns. \n\nI think having the compiler mutate the current namespace as it goes along is confusing, because it requires you to think about order of compilation. It requires non-local reasoning to figure out which var an unqualified symbol refers to -- not just looking at what's lexically-enclosing. This is unlike in clojure, where if you read through a file of function definitions all in one namespace, then you know how every symbol will be resolved simply by looking at its name (okay, with the exception of refers).\n\nWhat advantage does pixie gain by having in-ns be a special form that affects compilation state?\n","author":{"url":"https://github.com/joshua-g","@type":"Person","name":"joshua-g"},"datePublished":"2015-09-01T07:29:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/366/pixie/issues/366"}