Tom Fryers
Tom Fryers
The test failures were caused by some doctests calling ```rust Proj::new_known_crs(&from, &to, None) ``` where `from` is `&str`, so `&from` is `&&str`. Perhaps there is more code out there that...
I think the `TryFrom` implementation extension doesn't cause breakage, since that never accepted `&&str`.
I just find it a bit odd for `Proj` to ask for a reference if in the end it wants to own its input. (See [C-CALLER-CONTROL](https://rust-lang.github.io/api-guidelines/flexibility.html#caller-decides-where-to-copy-and-place-data-c-caller-control).) Having had another look,...
Having `Send` would make writing asynchronous code with Proj much easier. Could `PJ_CONTEXT` pointers be moved out of the `Proj` and `ProjBuilder` structs into thread-local variables? It would seem to...
This is now covered by `weasel_words.very`, I believe.
Yes, for debugging purposes I think you'd want to use `-g -Og`.
It isn't necessary, but it may be faster. The downside is it means the binaries aren't portable. I was assuming people were only using this script to build local binaries...
The same problem happens with `edition = "2024"`, too.
I'm using `rustfmt 1.8.0-nightly (7608018cbd 2024-09-29)`. I have `rustfmt.toml` (`edition = "2021"`), but running outside the project directory makes no difference. I’m passing source code to `rustfmt` on standard input,...
Better still: `echo | ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustfmt` is only 10 ms.