Semirix

I'm curious to know if there's been more progress on this.

Are you talking about a similar approach to serde, as outlined [here](https://serde.rs/field-attrs.html)? That would certainly make it look much cleaner.

This is easily fixed by adding some extra fields in the matrix. Here's an example config: ```yaml name: Build Godot on: push: {} pull_request: {} jobs: Godot: runs-on: ubuntu-latest strategy:...

> The suffix to use for macOS exporting is `.zip` or `.dmg`. `.app` can't be used directly (although an `.app` is contained within the generated ZIP). @Calinou Ah, so for...

@shepmaster The `try { ... }` block is the closest to what I idealised. I was unaware `try` was in nightly. If it gets stabilised, this proposal in my eyes...

@SOF3 > Whatever you want, don't use the `!` character for more things please. `!matches!()` is terrible enough. I agree that `!` is not the ideal syntax. I'm hoping the...

@SOF3 > I don't understand why it is `foo!.bar!` instead of `foo.bar!`. Can you define precisely if `foo!` is one expression or if `!.` is one operator, or is there...

@Lokathor Ah, my bad. I forgot about nested results. Whatever the syntax ends up being, having it positioned at the end is probably the best idea. @SOF3 > I don't...

Ah, I see I have missed an important part of the implementation. The idea is that this would be added to the top level `Raft` type like so: ```rust pub(crate)...

@drmingdrmer Sort of. It'll tide me over but it would be better to have more structured sequential event reporting.