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

named imports #5

Merged
merged 1 commit into from
Jul 20, 2019
Merged

named imports #5

merged 1 commit into from
Jul 20, 2019

Conversation

lukepighetti
Copy link
Contributor

This is just a concept. It's not Darty at all (some people might try to take off my head for suggesting this hahaha) but it does use a common approach I have seen in rxjs via TypeScript that helps to handle namespace issues since you're providing functions instead of classes with methods.

@renggli
Copy link
Owner

renggli commented Jul 20, 2019

Yeah, that looks a lot like TypeScript. It is not ideal, but I've seen this pattern in Dart as well.

Ideally the constructors and operators could be inserted directly into the base classes: dart-lang/language#40, dart-lang/language#41, dart-lang/language#42, dart-lang/language#177, dart-lang/language#309, dart-lang/language#8547.

@renggli renggli merged commit 218c536 into renggli:master Jul 20, 2019
@lukepighetti lukepighetti deleted the named-imports branch July 20, 2019 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants