Daniel Egger
Daniel Egger
@DaQue It's not too complicated, especially with documentation. Basically you'll have to fork the repository, then you click on the file you'd like to modify, click on the pen icon...
@DaQue I see only 1 PR (https://github.com/rust-embedded/discovery/pull/118) which already got merged.
No need to delete the forks, after a PR is merged you'll automatically get the options to delete the branch (in the PR) so you don't have outdated branches hanging...
Just curious: What's the use case for unwinding in embedded scenarios?
Makes sense, thanks for the explanation.
@bergus Lack of application control and accidentally ignored problems due to developer laziness. Possibly there're more.
> I always implicitely assumed that option 2 would be the one to go with. That's exactly the problem with that approach: It isn't done that way at the moment...
> Finally, I think forgetting to reset error flags might be a common user mistake which would also be fairly tricky to track down. Not sure what you mean by...
@bergus > I don't however get the point you're trying to make with "there's no way to verify it other than inspect the code or test it on the hardware."...
> What I mean is that with method 2, the responsibility to clear errors is on the HAL implementation author. This means that only a few well tested crates would...