Comments (2)
After talking yesterday I was thinking about this more and if we are calling getObjectMetadata
on the value returned from a .runtimeType
getter, then technically dart:_runtime library
and RecordType
were incorrect with the old type system too. That is the old internal representation and not what was returned from .runtimeType
in the old type system. We probably should have always reported dart:core
and Type
, as the class along with RecordTypeKind.
from sdk.
We probably never run into that case due to runtimeType
being a getter in the old system and not showing getters before in VSCode
from sdk.
Related Issues (20)
- Convert all formal parameters to named doesn't handle super parameters well HOT 3
- Convert all formal parameters to named offered when there are no positional parameters to convert HOT 3
- Convert all formal parameters to named changes optional named parameters to required HOT 2
- [macOS] OS::GetCurrentMonotonicTicks should probably use `CLOCK_UPTIME_RAW`. HOT 6
- Unable to create NativeCallback from function HOT 2
- DevTools server is not robust when it has multiple devtools clients connected to different apps
- Add a concept of trusted clients to the DevTools server HOT 1
- `dart analyze` should use LSP to communicate with analysis server HOT 1
- Analyzer hang related to `string.dart` HOT 2
- generated_plugin_registrant is adding _ to import file HOT 1
- [analyzer] Incorrect recursive instance creation in the constant context leads to analyzer not showing any new errors HOT 5
- extension type not compiling for flutter web HOT 1
- [bug-arm32] The variable of type int returns an incorrect value HOT 5
- Latest Chrome Browser no longer works with Twilio Video/Programmable Video, issue seems to originate in the DART:JS package HOT 5
- Type inference discrepancy HOT 6
- [dart2wasm] Implement structs backed by TypedData HOT 2
- Semantics highlighting gets shifted HOT 4
- IPV6 uri resolving creates invalid host HOT 1
- [analyzer] Incorrect completion for redirecting constructors HOT 4
- quick-fix for `use_named_constants` HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sdk.