Gino Valente
Gino Valente
For reference, `@dreamertalin` on [Discord](https://discord.com/channels/691052431525675048/1002362493634629796/1234987170205270079) provided some of their own use cases for such custom attributes: > If it helps any, here's a list of some use cases for annotations...
> Where `Range` would semantically mean "allowed value range". For common use cases like this, we could define "standard" types to encourage collaboration + overlap. That's a good point. I...
Okay I think I'll move this over to the typed proposal unless someone has any other comments/opinions. @cart I think we can make this work without the `@` prefix for...
Hm, one thing this new syntax doesn't protect against is duplicate attributes. I feel like that's a likely occurrence, so maybe we just ignore them? Maybe last attribute added just...
LGTM! We could consider forcing additional bounds (i.e. `PartialEq`) that we know most wrapped/saturated types implement so that we can register additional type data. But for now, I think we...
The `undo` portion is a little confusing to me. It sounds more like we want to detect a transition of a particular condition from `false` to `true` and only log...
> We should also decide if having `$condition` be `true` causes the `$expression` to be called every call or only the first time it's `true`. If we do this, it's...
> This runs the `$expression` the first time it's called, then when `$reset` is set to `true` then back to `false`, the `$expression` could be called once again. I think...
Closing in favor of #8014
Lol closed the issue instead of the PR 🤦♂️