semver-trick
factoriolab
semver-trick | factoriolab | |
---|---|---|
15 | 192 | |
414 | 433 | |
- | 1.6% | |
2.8 | 8.9 | |
25 days ago | 20 days ago | |
Rust | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
semver-trick
-
Making Rust supply chain attacks harder with Cackle
Let's say crate B depends on crate A with a pinned dependency, and uses one of its types in a public interface.
Crate C depends on them both. It now can't bring in updates to A until B does, and when B updates that's a breaking change, so it better bump its major version.
Take a look at this teick, for example, for foundational crates updating their major version: https://github.com/dtolnay/semver-trick
Now imagine that being an issue every single patxh update.
-
The module system is too confusing
Rust modules require a tiny bit more definition up-front, but they neatly decouple the module hierarchy from file layout so you can reorganize code however you like in future, and they support very fine grained control of privacy (such as being able to say pub(super) and pub(crate)). In extreme cases, you can even re-export symbols from one module in another without it counting as a breaking change, so you have even more options for evolving your project without breaking existing consumers. Look at the the semver trick as an example of how powerful this can be and how much freedom it gives library implementors. (And even if you're only a library consumer, wouldn't you rather be consuming libraries by implementors that had more freedom and power?)
-
My first year with Rust: The good, the bad, the ugly
A library author concerned about this can use the semver trick. TL;DR: if your current version is 0.42, you can do a 1.0 release, then do a 0.43 release that depends upon your 1.0 release and re-exports all the symbols.
-
Does Rust have any design mistakes?
I mean for all the parts of the standard library that do not change, one could presumably use the semver-trick.
-
Rust is hard, or: The misery of mainstream programming
The semver trick can help with libraries at least when they go to unify the ecosystem. Release new versions that replicate previous APIs in a compatible way while moving to the standard library implementation.
-
Roadmap
Because you still run into the problem that's been seen when various important crates upgraded and either didn't use the semver trick or had downstream crates specifying Cargo.toml version requirements too narrowly for it to be effective.
- The Rust SemVer Trick (2019)
-
This Year in Embedded Rust: 2021 edition
It's called the "semver-trick" [1].
[1]: https://github.com/dtolnay/semver-trick
- The Semver Trick
-
The chip shortage keeps getting worse. Why can't we just make more?
The JVM is 114MiB on my machine. A near-minimal ggez program in debug mode is about 100MiB,¹ and ggez is small for a Rust application library. When you start getting into the 300s of dependencies (i.e. every time I've ever got beyond a trivial desktop application), you're lucky if your release build is less than 100MiB.
Sure, I could probably halve that by forking every dependency so they aren't duplicating versions, but that's a lot of work. (It's a shame Rust doesn't let you do conditional compilation based on dependency versions, or this would be a lot easier. As it is, we have to resort to the Semver trick: https://github.com/dtolnay/semver-trick/ — not that many people do that, so it's functionally useless.)
¹: I can get it down to around 8MiB with release mode, lto etc., but that significantly increases the build time and only about halves the weight of the intermediate build files.
factoriolab
-
TIL: Do not underestimate the production you need to make even a trickle of module 3s! (Mini base tour)
here's another: https://factoriolab.github.io/
-
Vanilla 500spm Problems
Got everything built out for 500 spm using the online calculator (This one: https://factoriolab.github.io/) and when I was done I found a few issues.
-
~87% of iron is used for steel and green circuits
https://factoriolab.github.io/ is the same but better than Kirk McDonalds in many ways.
- Space exploration recipes
- Beginner here, is there any tips to make this like way smaller. At this point idek how ima do the other sciences
-
Is this basic rubber/plastic setup as clever as it seems ?
I recommend the factoriolab calculator for satisfactory it's very powerful.
-
Blueprints - black box or bulk single?
If you build everything correctly, there are no need to concern about the ratio of proliferator. Factoriolab is your friend to help you calculate how many of those proliferators are need.
- 248k mod and insane stone requirements?
-
can anyone tell some "golden ratios" for a beginner
Kirk's calc is superseded by https://factoriolab.github.io
-
[IR3] Are Burner Miners actually cleaner than Steam Miners when burning charcoal?
To calculate the cost of burner inserters, I used 286 swings per coal (from my own testing), and then added additional mines to a factorio calculator to account for supplying the burners. Then I calculated the burner swings needed to supply the additional mines, and added even more mines to supply that, and repeated that process three times, after which the the tenth's place did not change. These additional miners providing fuel are not counted for useful output. I did not count the negative pollution from forestries.
What are some alternatives?
lang-team - Home of the Rust lang team
FactoryPlanner - A mod for Factorio. Allows you to plan out your production in detail.
cargo-llvm-lines - Count lines of LLVM IR per generic function
yafc - Powerful Factorio calculator/analyser that works with mods
rust-base64 - base64, in rust
Foreman2 - Visual planning tool for Factorio
Thruster - A fast, middleware based, web framework written in Rust
factorio-lab-tools - Lua parser to build data and icons for FactorioLab base recipe sets
rust-quiz - Medium to hard Rust questions with explanations
factorio-blueprint-visualizer - A python library to artfully visualize Factorio Blueprints and an interactive web demo for using it.
serde - Serialization framework for Rust
FactorioSimulation - Multiple tools for factorio stuff, most notably the belt balancer analyzer.