Document external on the Functions page
#5478
Assignees
Labels
a.language
Relates to the Dart language tour
d.enhancement
Improves docs with specific ask
dev.interop
Relates to use of native code as part of your Dart app
e1-hours
Can complete in < 8 hours of normal, not dedicated, work
p1-high
Major but not urgent concern: Resolve in months. Update each month.
Comments
parlough
added
a.language
32 tasks
This was referenced Jan 19, 2024
Merged
MaryaBelanger
added a commit
that referenced
this issue
Jan 31, 2024
Fixes #5478 --------- Co-authored-by: Erik Ernst <[email protected]>
atsansone
pushed a commit
to atsansone/site-www
that referenced
this issue
Feb 1, 2024
Fixes dart-lang#5478 --------- Co-authored-by: Erik Ernst <[email protected]>
atsansone
pushed a commit
to atsansone/site-www
that referenced
this issue
Feb 9, 2024
Fixes dart-lang#5478 --------- Co-authored-by: Erik Ernst <[email protected]>
atsansone
pushed a commit
to atsansone/site-www
that referenced
this issue
Feb 20, 2024
Fixes dart-lang#5478 --------- Co-authored-by: Erik Ernst <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
externalkeyword isn't explained anywhere on the site. Right now, references of it point to the spec.With JS interop and extension type docs developing, I think it's important to have a high-level summary of
externalto point to when we're talking about it.I think the section should go on the Functions page, and be relatively high-level (description in the spec is good). Since it's highly platform dependent, we can just summarize it and point to interop docs (maybe use C and JS specifically as an example, until we have a interop overview page to point to instead).
The text was updated successfully, but these errors were encountered: