Julien Cretin

> I don't think a proc-macro can deliver the kind of efficiency that I'm hoping to achieve with a manual implementation. I don't see any theoretical reason it couldn't, but...

Just an update here. I have a basic design that I think works, but that's too much work for me to finish in the medium term. Maybe I'll pick this...

This is only working out fine right now as long as a custom MPU implementation is used. The default implementation does not enforce any alignment. Here's the bug (undefined behavior...

> Did you hit this bug in practice? If so I am curious to see how. I guess just using the default MPU config on a board with no MPU?...

There is no active work planned so you would indeed need to implement it. I'm a bit worried of such feature increasing the risk of users falling for typosquat attacks....

I'm not sure what you mean. You already can run the extension according to the bug report. Maybe you mean a custom development version? In that case (assuming Linux) you...

I don't know VS Code, but the PATH is in the wrong order, you want to search in the custom directories first: ``` export PATH=$HOME/dev/repos/taplo/target/debug:$PATH export PATH=$HOME/dev/repos/taplo/target/release:$PATH ```

Thanks for reporting this bug! I cannot reproduce though, so I'll assume for now that this is VSCode specific. In which case there would be 2 options: - VSCode sends...

This might be related to tags not being automatically created: https://github.com/tamasfe/taplo/pull/547#issuecomment-1947560805. But I just checked and it looks like the tags exist now, so maybe it's just a matter of...

It seems like not only the crates were not released but also the VS Code extension. Probably the same issue.