-
Notifications
You must be signed in to change notification settings - Fork 19
Conversation
Added an example as documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea, thanks!
bors r+
42: Add equivalent of dbg! macro r=adamgreig a=nickray I think this would be quite useful. Thoughts? Maybe it would be better for `dbg!` to be in core with somehow switchable implementation (semihosting, vcom, etc.), but I don't know how to approach that. Added CHANGELOG also for the missing one for #39 Perhaps some more documentation is needed? Co-authored-by: Nicolas Stalder <[email protected]>
Build failed |
Looks like we'll need to edition-2018ify this crate first. |
Interesting, I see no compilation errors (also explicitly setting 2015 edition), and successfully link into a 2018 edition example. Does Travis have some sort of strict mode? Or maybe it's because I use 1.37. I assume the edition update should be a separate request, right? If I go at it, anything I need to consider besides making it compile? |
Hehe, adding stable thumbv8m testing fixed https://travis-ci.org/rust-embedded/cortex-m-semihosting/jobs/575372081 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
bors r+
42: Add equivalent of dbg! macro r=adamgreig a=nickray I think this would be quite useful. Thoughts? Maybe it would be better for `dbg!` to be in core with somehow switchable implementation (semihosting, vcom, etc.), but I don't know how to approach that. Added CHANGELOG also for the missing one for #39 Perhaps some more documentation is needed? Co-authored-by: Nicolas Stalder <[email protected]>
We should probably mention edition2018 in the changelog but we can add that after. |
Build succeeded |
I think this would be quite useful. Thoughts?
Maybe it would be better for
dbg!
to be in core with somehow switchable implementation (semihosting, vcom, etc.), but I don't know how to approach that.Added CHANGELOG also for the missing one for #39
Perhaps some more documentation is needed?