Léo Gaspard

Hey @ngortheone! Unfortunately, I haven't had much time to give love to this project recently, so I wouldn't bet on it getting its first alpha cut before at least early...

BTW, seeing you active on #opensmtpd, I've just created a #yuubind on opensmtpd if you want to try having an easier chat -- can't guarantee I'll be online, though, I'm...

Sounds good to me! If at some point you feel like trying to contribute to yuubind feel free to let me know, but I do understand that it's easier to...

> * Why is the `pub(crate)` stuff needed? It allows other modules inside the same crate to access the value of these properties. The option structs are not defined in...

##### For options (structs) So I've seen `#[non_exhaustive]` used mostly on enums up to now. I guess non-exhaustive structs would require code like: ```rust let mut options: Options = Default::default();...

> Ah, so adding #[non_exhaustive] on a struct means you can’t use ..Default::default() anymore? That seems like a bad design. Right, that's my understanding of this sentence: > Non-exhaustive variants...

I understand your positions, and if I were writing javascript I'd follow the javascript conventions that are along the lines of using untyped objects to make the API ; but...

I just did what I could in #40 :) I didn't future-proof the pub structs in mdast.rs, because it didn't appear worthwhile to me. If you plan on often adding...

Got it, thank you! Do you think it would make sense to expose listing the supertypes of a node directly from the API, or should it stay a feature reserved...

I have no idea how to write elisp code, sorry :/ but installing treemacs and setting the emacs font to be large enough for the hint window not to fit...