Guess who's back?! The previous Mun release dates back over one and a half years. Since then - slowly but steadily - we've been working towards Mun v0.4.0 and it's finally here!
The core team is working on new features for Mun v0.4. The biggest feature will be dynamically sized arrays.
After the release of Mun v0.3 we are now looking at new features for the Mun v0.4 release. The biggest of which will be support for dynamically sized arrays.
It's been almost eleven months since the previous major Mun release. A lot has happened; in the world, in the Core Team members' personal lives, and with Mun. The ambitions that we set for Mun v0.3 were big - and the delays equally so - but we are excited to finally present Mun v0.3.0. This *tock*-release was focused on usability improvements; multi-file projects, a language server with diagnostics and autocompletion, and improvements to code quality and developer experience to name a few.
All features are in, our CI pipeline has been primed, the countdown has started. The Core Team is putting the final touches on documentation for Mun v0.3, but otherwise we are ready for lift-off!
It's been a long time coming, but the Core Team is closing in on the finish line for Mun v0.3. We are only a couple of pull requests away from locking the build for bug fixes and documentation. So start your engines!
Revitalized from the holiday break, the core team got cracking, resulting in half a dozen completed pull requests and even more in review. What's more, some fresh blood is dipping their toe in the Mun pond, as we kick off the new year.
December - again - was a slow month; holidays and day jobs keeping the core developers busy.
This Month in Mun is a little different from our usual posts. There's a very simple reason for that; we didn't manage to do much.
When Mun takes part in Hacktoberfest, there's one thing you can be sure of; lots and lots of pull requests. This month saw us finalise some big new features and refactors that inch us ever closer to a Mun v0.3 release.
The community and core team worked together on improvements to bring Mun closer to a new release. Work is also progressing to support multiple source files.
This month brings some big community and core team updates, paving the way for the release of all Mun crates - including the compiler - to crates.io.
A long list of community contributions, big marshalling performance improvements, technical debt flying out of the window, and a Rustacean Station podcast with the two Mun Core Team members. That can only mean one thing: yet another month of Mun development has come and gone.
After the dust settled of the Mun v0.2 release, the focus of this month has been on fixing several issues found by community members, improving the overall quality of the code base and working towards our next release: Mun v0.3
This month marked the release of a new version of Mun. It took us quite some time but after almost half a year, Mun v0.2 is out now! The most important feature of Mun v0.2? We now support hot reloadable structs.
After half a year of hard work by the Mun Community and Core Team, we are happy to present Mun v0.2.0. With the addition of hot reloadable structs, this forms a big step forward in terms of hot reloadability for the language.
In our efforts to finalise Mun v0.2, we've made a big push for the finish line. Through the combined efforts of the Mun Community and Core Team, we were able to release a record amount of new features, bug fixes, and improvements; the most anticipated new kid on the block being struct hot reloading!
The Mun v0.2 release is on the horizon, so we wanted to take this opportunity to delve a little deeper into this release's big newcomer: hot reloadable structs. Being able to effortlessly hot reload data was what we originally set out to do when designing Mun, so we are excited to share how we brought this feat about.
A lot of things that we cannot fully control are currently going on in the world. The Mun community and Core Team are trying to make the best of the situation and have once again made great strides; the recently obtained MOSS grant giving us an additional productivity boost!
We are very proud to announce that Mun has been awarded a $15K grant as part of the MOSS Mission Partners track. With Mozilla's generous support, we are able to boost the Core Team's efforts to finish hot reloadable data structures during the coming months.
The dawning of a new year is often marked by reflection and the conception of resolutions. We felt that the goals we had previously set for Mun v0.2 were still true, so with the help of our community we pushed forward with our plans.
December is often perceived as a month that emphasizes family and togetherness. The Mun community for one really did pull together, allowing the core contributors to focus on making data structures a reality.
November marked the first milestone release of Mun, providing the Mun community with a first chance to experiment with native hot reloading. Leading up to the release we mainly focused on CI, improving documentation, and bug fixes; but also made a few more additions.
In my Rust 2020 blog I tried to shy away from specific feature requests, instead zooming out to look at the Rust ecosystem as a whole. As a community, we've achieved great things but we should take care not to crumble under the weight of a scaling language and ecosystem. We all need to come together to ensure that Rust can sustainably scale - be it in large organisations, communities, or codebases.
We are proud to present Mun v0.1.0 - our first milestone release. As a language, Mun is still far from production-ready, but this release gives you a glimpse of what natively supported hot reloading will look like in the future.
Having built a runtime prototype and framework for lexing, parsing, type checking, and LLVM IR code generation; our goal for the remainder of October was to extend, polish, and stabilise this into a Mun v0.1 release.
After a successful first Mun jam, our ideas had advanced far enough that we felt ready to share our vision for Mun with the world.
As we finally found ourselves in the same country, our two-man team decided to get together for a Mun Jam.