Devin Pohl

> @Get-DevVed-YT shouldn't thirteen be `twelve+one`?? > Can you rewrite everynumber, so its > > ```rust > const one: i64 = 1; > const two:i64 = one+one; > const three:i64...

> is there a reason (that I'm not seeing) that this cannot be done with a macro that just implements the wrapping functions in a generated impl block? > Does...

Is crates.io commonly used for end-user programs? I thought that was only for libraries, but my experience is lacking. As for making this work with plugins, I do have a...

Oh, that's super cool. I had no idea the automated cargo distributions were a thing. I'll totally put this on crates.io at some point, but like I said it'll be...

> If a proper build.rs file were used (see here), then cargo --git method would work (although at that point it could be published to crates.io) This crate actually uses...

I've thought about this one a lot. The only way I'd implement config files is if I also revamped the plug-in system. I want to do this, but won't have...

Did you compile with the password plug-in enabled?

`const` members of traits are allowed, but make the issue a little more delicate. Actual methods would need to call the traits, complicating macros.

Turns out that a `const` member of a trait wouldn't help. `::` always resolves to the impl, so `Foo::f` is of the wrong type. This is okay the other way...

Webassembly is certainly a good idea. I plan on working on this (and `no_std`) immediately after finishing methods. Leaving this issue open as a reminder for me to get this...