Ingvar Stepanyan
Ingvar Stepanyan
@michaelficarra Yes, I already agreed that possible benefits of `raw` are clear :)
@impinball `kind` proposal sounds good at first glance, but better to move it to separate issue for relevant discussion. Could you please create one?
@impinball ``` < /^\/(.*)/([a-z]*)$/ > SyntaxError: expected expression, got ')' ``` I guess you missed at least one more escape character for `/`.
@carlsmith You might want to check out https://github.com/estools/ as a start (although that's surely a very limited list of tools, npm search should work better).
@mikesherov I'm also wondering if new Github's topics will help with discoverability over time.
> It would be quite unfortunate if people had to find this issue to figure it out. The README already says that it uses a custom syntax to describe its...
@michaelficarra That would be true if this would be the only reason for incorporating `raw`, but looks like it will be formalized in any case, so we can reuse it...
@fitzgen Thing is, some derives still accept options via extra attributes (for example, https://github.com/kwohlfahrt/enum-tryfrom), so I'm not sure if it's worth locking up to just trait name. Maybe accept a...
What do you think about the attribute approach then? (allowing any attributes to be appended) Should be still CLI compatible while allowing these more complex cases.
@fitzgen Maybe could use some other delimiter then, like "=>" or whatever?