wackbyte
wackbyte
Actually, the underlying issue was fixed upstream, but I think the setting still needs to be forwarded on the shields side?
Would it be possible for this to be automatically generated, probably as an action artifact?
You can test something that fails to compile by writing a doctest: ```rs /// ```compile_fail /// // ... /// ``` fn test_name() {} ``` A specific error code can be...
Since it compiles directly to Lua, MoonScript doesn't have a standard library that could include this. If you want a function similar to JavaScript's `prompt`, you could try this: ```lua...
I think this is happening because the order of `attrName`/`tagName` and `val` are reversed in your function parameters. You are using `(val, name)` when it should be `(name, val)`.
(Should the MSRV be increased?)
Seems like I shouldn't have to sign the CLA? The workflow isn't even there anymore.
i'm in favor of keeping this PR open over that one since it has merge conflicts
`use:` still does not validate that its argument *is* an expression, though. (I've updated the issue description to be more clear)
@microsoft-github-policy-service agree