Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aliases for namespaces #310

Closed
baronfel opened this issue Oct 20, 2016 · 2 comments
Closed

Aliases for namespaces #310

baronfel opened this issue Oct 20, 2016 · 2 comments
Labels

Comments

@baronfel
Copy link
Contributor

baronfel commented Oct 20, 2016

Aliases for namespaces [6323201]

Submitted by Daniel Bradley on 8/20/2014 12:00:00 AM
17 votes on UserVoice prior to migration

[ Edited by admin to apply to namespaces only, since as per comment you can already do this with module aliases ]
When using the ‘open’ keyword, allow a namespace being imported, to be assigned to an alias rather than the imported contents being made available to the current scope e.g.
namespace Foo = Some.Long.Path.To.Foo
This would be useful when importing namespaces containing modules/types with the same name to avoid fully qualifying all of the usages.

Response

** by fslang-admin on 2/10/2016 12:00:00 AM **

Thanks for the suggestion. It is quite a reasonable one and it has taken me a long time to mark this as declined. However I have now done so for the reasons listed below.
Don Syme, F# Language Evolution

Original UserVoice Submission
Archived Uservoice Comments

@toraritte
Copy link

Would anyone provide a short summary why this was declined? Both links above are broken and they were also never archived in Internet Archive. Thank you!

@smoothdeveloper
Copy link
Contributor

@toraritte https://github.com/fsharp/fslang-suggestions/blob/d48c35ce216e2bff148937ec028ad61e5c273fdf/archive/suggestion-6323201-aliases-for-namespaces.md

if you browse this repository root, and check "View all archived uservoice suggestions and comments" link, you'll be able to find most of the contents, despite it is not the most convenient, it is still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants