Tuấn-Anh Nguyễn

I'm adding a workaround in `tree-sitter-hl`: https://github.com/emacs-tree-sitter/elisp-tree-sitter/pull/201. Please check it out to see whether it works.

Yeah, live reloading support was generally a hack that accidentally worked on some versions of Linux/macOS. I think we should remove that part from the doc.

> I'm currently wondering why you brought in source the emacs-module.h header ( [here](https://github.com/ubolonton/emacs-module-rs/blob/master/emacs-module/include/emacs-module.h) ) and only took the 25 version of it. It seems that it prevents users from...

Yeah, either `to_` or `into_` sounds better. I'm leaning towards the former, but I'm not sure yet.

This was added in [release 0.13.0](https://github.com/ubolonton/emacs-module-rs/blob/master/CHANGELOG.md#0130---2020-03-11), but has not been stabilized/documented yet.

Rust 1.38 has [`std::any::type_name`](https://blog.rust-lang.org/2019/09/26/Rust-1.38.0.html#std:any::type_name), which makes this a lot easier. We may want to either bump the minimum Rust version, or add a new feature flag.

Do you have a particular use case in mind? Emacs guarantees to give dynamic modules utf-8 encoded byte sequences. `utf-8-validation` is mainly useful when you think you've encountered an Emacs...

I'm aware that a Lisp string is not necessarily utf-8. It can be either a "unibyte" string (byte sequence) or a "multibyte" string (internally encoded in a superset of utf-8)....

That means the assumption of the Rust binding was correct, but Emacs has (or used to have, I haven't checked this recently) a bug where `copy_string_contents` doesn't signal an error...

It can be done for the Rust bindings of NodeJS: https://github.com/GabrielCastro/neon-serde. I think it's possible for Emacs Lisp, too.