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
I wasn't able to find anything in the Maud documentation about the fact that splices can contain arbitrary Rust code, including compound expressions. I did stumble on #11, which contains a comment referencing ${ ... } before I created a bug about type inference, but it would be useful if the documentation had an example of this kind of thing. For instance:
This is also an example of the kind of thing that can fail when using Maud @let directives: they don't accept type annotations, so I sometimes get "the type of this value must be known in this context" errors.
The text was updated successfully, but these errors were encountered:
The documentation can be found at https://github.com/lfairy/maud-book. I'm too swamped with work at the moment to edit it myself, but if you have the time then I'd welcome a pull request.
I think @let not supporting type annotations is a bug. I've filed that as #73.
I wasn't able to find anything in the Maud documentation about the fact that splices can contain arbitrary Rust code, including compound expressions. I did stumble on #11, which contains a comment referencing
${ ... }
before I created a bug about type inference, but it would be useful if the documentation had an example of this kind of thing. For instance:This is also an example of the kind of thing that can fail when using Maud
@let
directives: they don't accept type annotations, so I sometimes get "the type of this value must be known in this context" errors.The text was updated successfully, but these errors were encountered: