DartBot

_This comment was originally written by @seaneagan_ --- That syntax could potentially be useful for something else: declaring a function's return value to be constant (at least when it receives...

_This comment was originally written by pi...@gmail.com_ --- Big +1 for this to happen. It would give a lot of new power to annotations, e.g.:   class MyVO {     @­Validator((value) =>...

_This comment was originally written by steffen.haup...@gmail.com_ --- Just found out that not even the [length] of a const String literal is a constant. I would really appreciate this to...

_This comment was originally written by @seaneagan_ --- Since function literals are anonymous, the only way to expose a constant one would be via a separate constant declaration of some...

_This comment was originally written by @Emasoft_ --- I agree with seaneagan here. There is no need for this. All methods should get this optimization automatically from the compiler if...

_This comment was originally written by @seaneagan_ --- @fmaud: It is useful to mark *declarations* as "const" to avoid someone referencing the declaration in a const-only context, and then you...

_This comment was originally written by @seaneagan_ --- I guess the only strange thing about auto-determining the constness would be that canonicalization would be dependent on whether a function literal...

_This comment was originally written by @Cat-sushi_ --- Yes, treating "const" as "new" is confusing. The villain of the confusion is newable constant constructor. So, hiding keyword "const" or "new"...

_This comment was originally written by @Cat-sushi_ --- In addition, on the other hand, my proposal is completely consistent in compile-time constant context, like other initialization list. I think, it...

_This comment was originally written by @Cat-sushi_ --- I think the current implementation compiles constant constructor without call site sequence. Is it true? And why? Is it related to start...