awint VS Amethyst

Additionally as far as I am aware, this is the first biginteger library to use what I think is called "separated storage and reference types". Similar to the way that Rust has storage types like [T; N], Vec , and String and reference types like [T] and str, my library has the storage types ExtAwi and InlAwi, with the common reference type being Bits. Bits uses some DST magic to achieve only single pointer indirection while being able to take advantages of Rust's mutable and immutable reference mechanics. Parts of the crate are admittedly hacks and use a lot of unsafe to achieve these things performantly, but I have a drawn on my previous numerical fuzzing experience and built a huge test suite (see `testcrate` in my repo) with purpose built tests for every function that is run under MIRI, debug mode with plenty of debug assertions, and release mode with a large number of iterations.

I just published my awint system of crates today. I have a no_alloc_test crate in the repository that builds and links the main crate to make sure that no dependency on an allocator is brought in (building the main crate is not enough, it seems that the checks for an allocator only occurs when linking to a building binary). When I follow the exact sequence of instructions that the `no_alloc_build` job in the `.github/workflow` file takes, it works first time on a local machine (specifically, Debian WSL 2 with a freshly downloaded rustup), but it fails with linking errors on the Actions CI run. How do I debug this issue?

Yep, we do this, it works great! We stole it from hecs and Amethyst before us. There's a nice write-up of the theory in the scheduler rework the team has been working on for the past few months.

Rust also has seemingly better libraries for the purpose. Both Bevy and Amethyst are available, and plenty more.

Amethyst

I recently stumbled upon a short YouTube video of somebody building a roguelike game in Rust. From there, jumping from resource to resource, I ended up going through (part) of this massive (and awesome) tutorial by Herbert Wolverson about his Rust library bracket_lib. In this tutorial, Wolverson builds a roguelike game with colored text characters. After reading through, I felt like writing another type of game in Rust, so I looked at the available Rust game engines. The most popular, seems to be Amethyst, but it looks like they halted their development efforts. Second in line was Bevy. People are using it, support for Android and iOS is on the way, uses an ECS and have some usage examples: looks good.

Depends on my goals. I year ago I wanted to learn rust, so I used piston for a gamejam. (There are several rust engines including bevy, piston, amethyst. They probably vary in quality, features, and constraints.) Piston was a terrible experience because compilation is slow even on that tiny project.

And there's already a couple of surprisingly full-featured 3D engines already out there. Most notably Amethyst.

View on GitHub

Is anyone having this problem? I can't connect to rocket.rs, actix.rs and amethyst.rs servers. I would play at https://tera.netlify.app/, but people out there is really toxic. I heard that Rust is getting an update while playing in a Rust server, just then rust server freezes and goes down.

Or should I jump directly in one of the bigger engines like Amethyst, Bevy or other?