This was a good, short read. Worth the time.
It's time that we admit to deaf people that music isn't real. The joke has gone too far.
Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn't be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.
I'd love to include my wave function collapse library, but examples of its usage in games is lacking atm. I've thought of a couple games that could be made that utilize the concept, but I haven't prioritized them.
For those that are interested: https://github.com/AustinHellerRepo/WaveFunctionCollapse
How does it handle multiple potential outcomes?
Example: unformat!("a {} b {} c", "a x b b y c")
Would it return Some(("x b", "y")) or Some(("x", "b y"))?
It's still useful when it's wrong because it can give you the jist of what should be done. If it uses a library or function that doesn't exist, you'll still be informed as to what it was intending for the process at that point. I've often gone and just replaced the made-up code with custom code that does the same thing.
It's surprising how useful ChatGpt is in these situations. Honestly, it's a great general purpose search engine.
Thanks for the suggestions. I appreciate it.
Every so often rust-analyzer in VS Code doesn't use the latest code after a cargo update and the only way I've found to fix it is a cargo clean. This means that I have to wait 5 minutes for the next build, painful. Just because of one project update. I would LOVE a faster build.
Extra info: the updates come from my dependencies that utilize my private repositories via a git = "[path]". The rust-analyzer is pulling from a cache or older version for some reason and I don't know where it is or why.
I would agree. Only if the performance is extremely similar but the readability (for some reason) is significantly better for the recursive solution would I choose that.
Rust, easily.
I love any reduction in build times. This is great news.
I'm hoping we don't have to, but the only example I saw utilizes unsafe code.
I spent a couple months creating a modular wave function collapse library that solves any kind of constraint problem where you can specify the collapse algorithm to match the problem. It's domain-independent since it uses generic "nodes" (graph nodes that can be of any predefined state) that have relationships with other nodes.
There are a few examples, so please feel free to experiment. If you can answer the questions listed out in the readme's Usage section, you'll have no trouble following an example similar to your problem's domain.
Cursorless. It's a spoken-language programming interface that allows the programmer (of basically any language) to use specific words to target existing text, move the underlying cursor/selection relative to that target, and then run a specific modification. Think of VIM but for voice. It runs in VSCode atm as a couple extensions along with an install of the audio tool Talon. https://www.cursorless.org/
My current favorite is mostly Rust-based with the tide crate, tide-jsx crate, vanilla JS, postgres crate, and Postgres in Docker. Super easy, super fast (to develop and run), but I haven't made any large web projects with this stack yet, just small stuff.
I was thinking the same thing when I was trying to use the new base64 code instead of the deprecated version: it's unnecessarily complicated. I remember thinking "why is this so hard, so convoluted?".
As someone who learned a lot from C++ and that now loves Rust, this annoys me.