TechiePi

> It might be useful to use this as a tracking issue for the examples with a [task list](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists#about-issue-task-lists) in the body of the issue, but would require creating a...

CI fails because the changes done in #74 have not been _back_-ported here

This last commit adds support for the tags that remained untranslated. Further examples of tags that are now translated > ### Return values  > ### Clickable references  >...

(https://github.com/rust3ds/ctru-rs/pull/75#issuecomment-1272537447)

Are going to be a new version? Or no? D:

Maybe this is _somewhat_ off-topic, but I think it would be a good idea to generate and publish the Rustdocs of ``ctru-rs`` to GitHub Pages on push, that way is...

> the crates get published (which I hope will coincide with the merge of the thread-related features) In that case, you're right, that won't be needed

Looks like we should add a guide about setting up a dev environment

And obviously, if this idea is approved I will create a PR with the workflow

Great! I'll be outside my home for a few days, but when I come back I'll start working on this feature