It would be nicer as a builder library to allow for users to extend our classes and allow them to leverage our builder while not adding the user's custom logic into our builder. This means that we would need the ability to store ConstantReaders and DartObject?s within memory.
We have all the needed functionality currently with the dart:mirrors library (which currently has usage by the TypeChecker). This could be listed as an unstable functionality (as dart:mirrors is listed as unstable) until a new direction is found (be that metaprogramming etc). This would give builder package maintainers the ability to make some of our functionality more flexible, while not adding to the maintainers burden.
An example of what this would look like is available in #679.
It would be nicer as a builder library to allow for users to extend our classes and allow them to leverage our builder while not adding the user's custom logic into our builder. This means that we would need the ability to store
ConstantReaders andDartObject?s within memory.We have all the needed functionality currently with the
dart:mirrorslibrary (which currently has usage by theTypeChecker). This could be listed as an unstable functionality (asdart:mirrorsis listed as unstable) until a new direction is found (be that metaprogramming etc). This would give builder package maintainers the ability to make some of our functionality more flexible, while not adding to the maintainers burden.An example of what this would look like is available in #679.