Mateus Felipe C. C. Pinto

@eernstg I'm considering this as a viable alternative to introduce phantom types to a class without breaking it. In this case, it wouldn't require any default values, but its usefulness...

> I don't think this issue presents a specific proposal, it's a 'request' rather than a 'feature' issue. Yeah, I am aware. I asked because I thought of writing a...

@eernstg wrote: > Does that work for your case? Hmm, not really. This would work if the client wouldn't ever want a different phantom type, but let's introduce a new...

> The syntax of `T default D` is okay, nothing special and easy to understand, but it's also quite long. It could definitely work, without introducing many reading problems for...

> People don't do generics if they are beginners in a language or programming. I don't agree. People who are beginners in programming in general may not use generic, but...

@Wdestroier This is one of the reasons why I avoided dealing with inference in my proposal. IMO, we shouldn't infer the default value based on the constructor. But, if we...

As far as I understand, `values` is not part of the `Enum` interface. This is the reason why you can't use it in an extension, mixin, or anything that receives...

Should we take advantage of https://github.com/dart-lang/language/issues/581#issuecomment-2259691898 and add octal literals? It seems @srawlins patch could be easily adapted to also solve this one.

@fkettelhoit In these cases I will simply use `.then`, as function chaining is way clearer than `await` chaining... ```dart final someChild = await db.get(someId) .then((o) => o.children) .then((o) => o.first.children)...

> But sure, there are cases where this could be needed (e.g. public nullable properties on objects)". > This is not justifiable. Nullable properties on objects should also be promoted,...