Weekly Release - Breakthrough
Last week, I wrote that I might be in the middle of a breakthrough, in regards to cleaning up the object construction code (#1249). Work is still ongoing, but so far there's every indication that my optimism was warranted, and I have indeed found the solution to the biggest problem that I've been battling with for the last months!
I still need to wrap this up, but I expect that won't take much longer now. I've posted an update in the issue that summarizes the current state and what's next.
Meanwhile, @danieleades has improved the codebase by fixing some non-default Clippy lints, and @zthompson47 addressed a potentially confusing error condition, by making sure there's a proper error message, if the RUST_LOG environment variable can't be parsed.
Sponsors
Fornjot is supported by @webtrax-oz, @lthiery, @ahdinosaur, @Yatekii, @martindederer, @hobofan, @thawkins, @bollian, @rozgo, @reivilibre, and my other awesome sponsors. Thank you!
If you want Fornjot to be sustainable long-term, please consider supporting me too.
End-user improvements
Improvements to Fornjot and its documentation that are visible to end users.
- Fail, if RUST_LOG is invalid (#1435; thank you, @zthompson47!)
Ecosystem improvements
Improvements to Fornjot components that are relevant to developers building on top of those. These have an indirect effect on end users, through fixed bugs and improved robustness.
fj-kernel
- Improve behavior around validation failures (#1417, #1418, #1436)
- Continue cleanup of object construction code (#1419, #1423, #1428, #1429, #1430, #1432, #1433)
Internal Improvements
Improvements that are relevant to developers working on Fornjot itself.