Robert Gabriel Jakabosky

There are a few places in the `auth/providers/password/*.go` that incorrectly use `auth_identity.Basic` instead of `auth_identity.AuthIdentity`. I was able to get the demo to work by changing `Basic` to `AuthIdentity`. Might...

I think the correct fix is to change the type on line 17 from `Basic` to `AuthIdentity`: https://github.com/qor/auth/blob/2bfb79d9618566322a4e5e9b6664eefb9f49f427/providers/password/handlers.go#L17 Change to: ``` authInfo auth_identity.AuthIdentity ```

I was getting that same error before bevy 0.11 release. But now I get this when trying to import a function that ends with a digit: ``` ERROR bevy_render::render_resource::pipeline_cache: failed...

I think my results are from about 2 years ago. I will try to make some time this week to re-run the benchmarks. It is possible that `wasmi` has improved...

> > Since Rust doesn't guarantee tail-calls, the method used by `wasm3` can't be used in Rust. > > While Rust does not support guaranteed tail-calls we can still use...

I just tried out the master branch of `wasmi` and tested both v0 and v1. My original benchmarks were just using the `time` command for total run time. For `wasmi`...

Also this is the `fib.wasm` file I used: https://github.com/Neopallium/s1vm/blob/master/fib.wasm Forgot to add it before.

Not sure why wasmi v1 was slower then v0 for me. I didn't have the time to fully port the `invoke.rs` example from v0 to v1, so maybe I made...

> It seems you were not using the following `Cargo` profile for compiling your `invoke` binary: > > ```toml > [profile.release] > lto = "fat" > codegen-units = 1 >...

> > I am looking forward to Rust adding support for proper tail-calls. The main reason I don't try using tail-calls in Rust is because they only work in release...