You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2019. It is now read-only.
ns-name has a distinct purpose, [Namespace] -> Symbol which is distinct from name being [Named] -> String. While most uses of ns-name were of the form (name (ns-name (the-ns ...))), that doesn't mean that dropping ns-name to ^:deprecated status was a great idea.
A better change would have been to move the old Namespace.getName():Symbol to Namespace.getNamingSymbol():Symbol or something and then to preserve ns-name using the explicit Symbol getter.
The text was updated successfully, but these errors were encountered:
Deprecating ns-name was a mistake, since it serves a unique purpose with
respect to name, being to fetch the naming _symbol_ rather than the
naming _string_.
Fixes#47
Deprecating ns-name was a mistake, since it serves a unique purpose with
respect to name, being to fetch the naming _symbol_ rather than the
naming _string_.
Fixes#47
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ns-name
has a distinct purpose,[Namespace] -> Symbol
which is distinct fromname
being[Named] -> String
. While most uses ofns-name
were of the form(name (ns-name (the-ns ...)))
, that doesn't mean that droppingns-name
to^:deprecated
status was a great idea.A better change would have been to move the old
Namespace.getName():Symbol
toNamespace.getNamingSymbol():Symbol
or something and then to preservens-name
using the explicit Symbol getter.The text was updated successfully, but these errors were encountered: