Closed JKRhb closed 1 year ago
Since it's already merged maybe we could wait for the fix to be released? Just using name
looks a little prettier :)
Since it's already merged maybe we could wait for the fix to be released? Just using
name
looks a little prettier :)
Yeah, that's true :) However, it seems as if the bug is still present in Dart 2.17.5 (see here) :/ I hope it will be part of a 2.17.6 release, otherwise we might need to increase the required version to 2.18 if it is only included then.
In the current Dart version, using a
name
field in an enhanced enum (as we currently do in theOptionType
enum) causes a segmentation fault (c.f., https://github.com/dart-lang/sdk/issues/49296). Although this will be fixed in the next version, this PR simply changes the identifier of the name in question as a workaround to avoid segfaults.