diff options
| author | bors <bors@rust-lang.org> | 2018-11-26 01:46:18 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-11-26 01:46:18 +0000 |
| commit | 423291f14bbb820265b2bbf33d6fffb044035b86 (patch) | |
| tree | d5a500b213463efcafdb9d4bfd747e53f64f7ed5 /src/rustllvm/RustWrapper.cpp | |
| parent | c14ab13e618958bcb353b4e3c2eb2228475aa1ab (diff) | |
| parent | 121e5e806e41c4825fc4a25ad45d2585d1058165 (diff) | |
| download | rust-423291f14bbb820265b2bbf33d6fffb044035b86.tar.gz rust-423291f14bbb820265b2bbf33d6fffb044035b86.zip | |
Auto merge of #55705 - ethanboxx:master, r=SimonSapin
Make `ParseIntError` and `IntErrorKind` fully public Why would you write nice error types if I can't read them? # Why It can be useful to use `match` with errors produced when parsing strings to int. This would be useful for the `.err_match()` function in my [new crate](https://crates.io/crates/read_input). --- I could also do this for `ParseFloatError` if people think it is a good idea. I am new around hear so please tell me if I am getting anything wrong.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
