Assertions for Invalid Riverpod Syntax

[whitemagehealing]

I'm sorry if this does not make sense or isn't even possible in Dart, but should there be asserts for the following inside of StateNotifier?

1. no state.copyWith() detected for whatever type state is.
   // Not sure if detecting lack of an interface implementation is possible in ANOTHER class.

2. state.mylist[state.mylist.length - 1] = 27;
   // should either automatically realize a copy for everything and only change this one param OR just assert that something that is immutable shouldn't be mutated. It seems silly to write a whole new temporary list, change that one value and pass it all into the copyWith(); however, I'm guessing that this is a current limitation with Dart. I have @immutable over my state class, but no error or assert is thrown. :(

3. state is not detected as immutable.
   // Again, maybe this is just all not possible yet, and is a limitation of Dart.

I understand if these are all limitations of Dart, but if Dart somehow removes these limitations, do these sound like reasonable expectations?

[rrousselGit]

As an assert, it's not really possible.

With custom lint rules, it's possible though. But that's more complex, so it'll take time before these are available

[whitemagehealing]

Okay, thank you so much for that explanation! I had my suspicions about the language not allowing it, because the scoping and traits seemed unusual for a compiler to detect, but it's great to know that there's something that does exist that could make it semi-possible.

Have a wonderful day!