You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See now closed issue #3205, as well as the discussion on PR #3375 and the discussion on PR #3420, among others.
This exercise appears to lend itself to lambda abuse, rather than encouraging the practice of enums, as was the intent from the earlier versions.
We need to somehow rework or rewrite this exercise to be more enum -forward or more encouraging of not assigning names to lambdas. Or we deprecate this version in favor of one that uses a string for the category rather than a constant.
Not clear on next steps, but this issue should serve as a start for re-work.
The text was updated successfully, but these errors were encountered:
See now closed issue #3205, as well as the discussion on PR #3375 and the discussion on PR #3420, among others.
This exercise appears to lend itself to
lambda
abuse, rather than encouraging the practice ofenums
, as was the intent from the earlier versions.We need to somehow rework or rewrite this exercise to be more
enum
-forward or more encouraging of not assigning names tolambdas
. Or we deprecate this version in favor of one that uses a string for the category rather than a constant.Not clear on next steps, but this issue should serve as a start for re-work.
The text was updated successfully, but these errors were encountered: