daxpedda

No you are absolutely right, which is why I said earlier I should get my priorities straight :sweat_smile:! But just as a reality check: I don't believe a lot of...

I'm gonna go ahead, rebase this and merge it.

There are no official plans for this. Generally speaking there isn't much to say here, its just going to be a whole lot of carefully going through the code and...

Sure! Will work on a review ASAP when its ready!

Yes, expanding our testing to older compiler versions (maybe just MSRV and beta) would be great, I'm happy to look at any improvements! We should also look into testing with...

@calebcartwright friendly ping. Would love to continue working on it if [ytmimi](https://github.com/ytmimi) is too busy.

I'm strongly in favor of just following the Cargo convention. Cargo can figure out how to solve this specific problem. We should probably follow https://github.com/rust-lang/cargo/issues/6790 and see if this works...

> On a different note: static properties. Static properties and readonly variables sometimes use SCREAMING_SNAKE_CASE similar Rust `const` and `static` variables. We should probably detect that, right? > > In...

> > In which case wouldn't we be looking at something like auto_jsify doing it all in one go instead of having multiple ones? > > Not really. My point...

> No. In JS, the best we have are [common](https://www.robinwieruch.de/javascript-naming-conventions/) [naming](https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Writing_style_guide/Code_style_guide/JavaScript#function_names) [conventions](https://google.github.io/styleguide/jsguide.html#naming). Hm, that's bad. > This means that names that are already in PascalCase, camelCase, or SCREAMING_SNAKE_CASE, are most...