Russell Johnston

Ideally `?` could just be extended to provide stack trace support directly, rather than relying on the ability to override `try!`. Then it would work everywhere.

An additional benefit to making this into a clang plugin is that it would work with a wider variety of existing clang installs. For example, I have a clang toolchain...

Isn't that the wrong ordering for the narrative structure? It should be: 1. `x` borrowed here 2. write to `x` occurs here, while borrow is still in active use 3....

IMO that one combined with numbering would be the easiest to follow.

If awaiting is going to be the default, it needs to be the default everywhere, not piggybacked on `?`. (Getting a future rather than awaiting would then need a syntactic...

This thread has some more discussion, based on Kotlin's flavor of async/await: https://www.reddit.com/r/rust/comments/6zy8hl/kotlins_coroutines_and_a_comparison_with_rusts/ #### Treating async like `unsafe` (an effect) One idea that offsets the "magic" of inferring `await!` is...

`async` is basically already the inverse effect, and is already propagated through traits, etc. because it requires changes to function signatures (returning a Future in today's implementation; being an implementation...

FWIW, I don't think using `trait` is actually that confusing. Type aliases do not define new types themselves, and yet we use `type Foo = ..` syntax. Trait aliases may...

There is currently only support for Win32 and WebAssembly. If you (or anyone) is interested in adding Linux support, the entry point to the platform implementations is here: https://github.com/rpjohnst/dejavu/blob/a012bf5/runner/src/lib.rs#L22-L36 The...

I'd like for the project to have small, purpose-built, per-platform backends. The interface between engine and platform is a single data structure containing GM-specific things like input events and sprite...