-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Update documentation to cover non-function type aliases #44965
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
Comments
We don't have any internal documentation about general language features--except for null safety. So I think there's nothing to do for internal documentation.Thanks. |
For external docs, I think we need to update https://dart.dev/guides/language/language-tour#typedefs |
@kwalrath, perhaps we should communicate a bit about this? The text in https://dart.dev/guides/language/language-tour#typedefs needs a few updates, and then an extension: At first, we should be a bit more general now that a type alias can define an alias for any type, not just a function type. Maybe we could do something like the following:
-->
We may be able to reuse the old example using |
I'd love to start with a simple example, like: typedef IntList = List<int>;
IntList il = [1,2,3]; |
@kwalrath any updates? |
This won't be in a stable release for a while, correct? We often don't cover features until they're in a stable release (with the exception of features where we want feedback or that need a lot of work for our readers to incorporate). |
@kwalrath This is targeting the next dart stable release |
@kwalrath Any concerns about this being ready for when we hit stable? |
Nope |
Moving this to April |
@kwalrath Any update on this doc? |
We expect to have the docs for stable, not beta. |
@kwalrath I'm moving this to June |
@mit-mit we'd talked about maybe using JsonMap instead. Did you find that example? |
Link to site-www |
closing as dart-lang/site-www#2937 is closed |
This issue tracks support of the non-function type alias feature. See the enclosing meta-issue for details.
@kwalrath @davidmorgan do you want separate issues for internal/external docs? Who else should I loop in here?
cc @franklinyow @mit-mit
The text was updated successfully, but these errors were encountered: