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
[api.dart.dev] Update incorrect URLs in the Dart SDK sources
The old site supported api.dart.dev/stable/<page in the latest version>
links. These currently don't work, but the correct link omits the
`/stable/` path component.
Even if we add redirects to make the old URLs work, we still want to
update sources with the canonical URLs.
CoreLibraryReviewExempt: Documentation change only.
Fixes: #57110
Change-Id: I0b20bfa875db5ce62362a02e884d7d43b0efc73e
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/395961
Commit-Queue: Ivan Inozemtsev <[email protected]>
Reviewed-by: Ivan Inozemtsev <[email protected]>
Commit-Queue: Alexander Thomas <[email protected]>
Auto-Submit: Alexander Thomas <[email protected]>
Copy file name to clipboardExpand all lines: docs/gsoc/Dart-GSoC-2023-Project-Ideas.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ Successfully completely this project will likely involve:
119
119
120
120
* Determining exactly what APIs should be make available in Dart.
121
121
* Creating a JNI bindings for those APIs using [`package:jnigen`](https://pub.dev/packages/jnigen).
122
-
* Creating a higher-level interface over the JNI bindings e.g. so the Dart developer can work with [Dart URIs](https://api.dart.dev/stable/dart-core/Uri-class.html) rather than [java.net.URI](https://developer.android.com/reference/java/net/URI).
122
+
* Creating a higher-level interface over the JNI bindings e.g. so the Dart developer can work with [Dart URIs](https://api.dart.dev/dart-core/Uri-class.html) rather than [java.net.URI](https://developer.android.com/reference/java/net/URI).
123
123
* Creating a [`package:http``Client`](https://pub.dev/documentation/http/latest/http/Client-class.html) implementation using the interface above.
124
124
* Verifying that the `Client` implementation passes the [conformance tests](https://github.com/dart-lang/http/tree/main/pkgs/http_client_conformance_tests).
125
125
@@ -135,19 +135,19 @@ A good project proposal will describe what Java APIs are necessary to implement
135
135
136
136
137
137
138
-
## **Idea:** Refactor Plus packages to utilize new Dart 3 language features
138
+
## **Idea:** Refactor Plus packages to utilize new Dart 3 language features
**Description**: Dart 3 introduces a few new language features. There are several features such as Records, pattern matching and new direct platform library interop which potentially helps to improve code readability and better API design for packages.
145
+
**Description**: Dart 3 introduces a few new language features. There are several features such as Records, pattern matching and new direct platform library interop which potentially helps to improve code readability and better API design for packages.
146
146
147
147
We would like to explore the possibilities of the new language features that could help to improve packages and create a new API (potentially) or refactor internal coding that make the package to take full advantage of Dart 3. We would like to also prepare a guideline after this refactoring for other maintainers to figure out what could be improved or changed.
148
148
149
149
We are using [Federated plugins](https://flutter.dev/to/federated-plugins), therefore this is likely to involve:
150
-
150
+
151
151
* refactoring `platform_interface` class for each package,
152
152
* refactoring app-facing and platform-specific-implementation packages,
153
153
* potentially removing native code and replacing it with direct dart API calls,
Copy file name to clipboardExpand all lines: runtime/docs/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ However the main difference between these lies in when and how VM converts Dart
68
68
69
69
Any Dart code within the VM is running within some _isolate_, which can be best described as an isolated Dart universe with its own global state and _usually_ with its own thread of control (*mutator thread*). Isolates are grouped together into _isolate groups_. Isolate within the group share the same garbage collector managed *heap*, used as a storage for objects allocated by an isolate. Heap sharing between isolates in the same group is an implementation detail which is not observable from the Dart code. Even isolates within the same group can not share any mutable state directly and can only communicate by message passing through *ports* (not to be confused with network ports!).
70
70
71
-
Isolates within a group share the same Dart program. [`Isolate.spawn`](https://api.dart.dev/stable/dart-isolate/Isolate/spawn.html) spawns an isolate within the same group, while [`Isolate.spawnUri`](https://api.dart.dev/stable/dart-isolate/Isolate/spawnUri.html) starts a new group.
71
+
Isolates within a group share the same Dart program. [`Isolate.spawn`](https://api.dart.dev/dart-isolate/Isolate/spawn.html) spawns an isolate within the same group, while [`Isolate.spawnUri`](https://api.dart.dev/dart-isolate/Isolate/spawnUri.html) starts a new group.
72
72
73
73
The relationship between OS threads and isolates is a bit blurry and highly dependent on how VM is embedded into an application. Only the following is guaranteed:
0 commit comments