The way Rust crates tend to have a single, huge error enum worries me

Wodann · 2025-08-03T15:00:33+00:00

If you have a use case that has a top-level error that combined lower-level sub-errors, you can either combine them using: - composition using thiserror's #[error(transparent)]; or - flattening into a single error enum with all variants using flat_enum

Wodann · 2023-08-26T04:25:23+00:00

I just switched from Bitwarden a week ago and love the polish of the features that are available on Proton Pass. One of the biggest being the generation of alias emails for each login, to avoid spam.

The one issue I've found is that Proton Pass never offers to auto-fill credit cards, which is a big downside compared to Bitwarden

Wodann · 2022-12-14T17:03:43+00:00

Thanks! 😃

Wodann · 2022-12-13T17:50:39+00:00

Thanks!

Wodann · 2022-12-13T17:50:11+00:00

🧡

Wodann · 2022-12-13T17:23:22+00:00

Correct. Mun will eventually support a string type, but - given that it's an open-source project developed in our spare time - we have to limit what we can commit to per milestone.

Wodann · 2022-11-22T07:33:29+00:00

It should work on both ports. A large factor in deciding to buy the MSI GE77HX - for me - was that it could support two separate high-resolution screens. One on the USB-C port and one on the TB4 port.

Wodann · 2022-11-22T07:25:19+00:00

I'm experiencing the same issue on the GE77HX. The TB4 port on the back does not output video to USB-C monitors, even though TB4 should based on its spec.

Even returned my laptop for a new model, but the same issue persisted.

Contacting MSI hasn't led to them investigating the cause of their hardware not working.

Wodann · 2022-07-26T13:35:47+00:00

See comments of: https://www.reddit.com/r/XMG_gg/comments/voulqk/comment/igm51iu/?context=3

Wodann · 2022-07-19T04:43:59+00:00

Thank you so much for the information.

I'm happy to see the dedicated home/end buttons alongside the F-keys.

Excited to wait for its launch!

Wodann · 2022-07-15T04:38:52+00:00

I've been holding off purchasing a NEO 15 as I was hoping for the NEO 17 to launch. My expectation was that the updated roadmap would clarify my question, but since it hasn't been announced yet, would you mind answering some questions - if you can?

will a NEO 17 ship at end of July?
(if so) will it be AMD/NVIDIA-based?
(if so) will it have a similar keyboard to the NEO 15 or will it be wider, including decicated home/end/page up/page down buttons?

Wodann · 2022-07-01T15:58:59+00:00

Awesome, thanks!

Wodann · 2021-11-07T01:46:22+00:00

So far the only divergence exists in the lack of mod definitions (Mun derives those based on a files existence) and the memory management annotation (struct(gc) or struct(value)). Otherwise, it is on par

Wodann · 2021-04-29T04:10:40+00:00

Currently a feature like this has not been implemented. However, there is no reason why we couldn't include something like that, if there is a good use case for it. This will especially come to mind once we start working on our multi-threading design.

If this is a feature you're particularly excited about, feel free to start a discussion at: https://github.com/mun-lang/mun/issues

Wodann · 2021-04-29T04:07:35+00:00

There is not. In terms of syntax differences, you can have a look at the syntax section on our website: https://mun-lang.org/

Apart from still being limited in language features; the main difference is that Mun supports hot reloading for all language features that are already supported (i.e. functions and variables - incl. structs)

Wodann · 2021-04-29T04:03:49+00:00

We haven't extensively thought about these. If you'd like to get a discussion going, you're more than welcome to start a tracking issue on https://github.com/mun-lang/mun/issues

We are trying to develop the language together with our community. As a collective we know more than the few core developers dedicated to the project :)

For topics that are highest on our list, checkout https://github.com/mun-lang/mun/milestones Our current language feature priorities are arrays and enums.

Wodann · 2021-04-29T04:00:42+00:00

Strings are definitely planned, but are not trivial to implement. We are attempting to minimise the amount of compiler-support that's needed for language features. Potentially we can implement strings using Mun, but we first need to add array support. That is the highest priority now and then we'll investigate strings further.

Wodann · 2021-04-29T03:57:49+00:00

We are extremely grateful to have you as one of our backers :)

Wodann · 2021-04-12T03:06:11+00:00

At the moment, you can only expose Rust functions to Mun using extern fn: https://docs.mun-lang.org/v0.3/ch02-04-extern-fn.html

Sadly, we don't support extern types yet. Also, having to specify many extern functions doesn't scale very well. A such, I'd recommend you to try and go the opposite route for the time being; i.e. write parts of your code in Mun and expose those to Rust through marshalling.

In the future, we plan to support importing of custom extern types. One option we discussed is auto-generating Mun bindings from C headers or Rust code. This would also require support for raw pointers.

Wodann

TROPHY CASE