Waleed Khan 76974a9050 build: suppress unstable_name_collisions warnings on stable ... Originally, I had thought that these warnings would only potentially show up in nightly because there was a feature which exposed these functions, and we would be able to enable that feature and conditionally not define the conflicting methods. But it looks like these warnings also show up in stable. I've just suppressed each of them individually. Other options would be to rename them and just make them wrapper methods, or to disable `unstable_name_collisions` warnings at a higher scope (possibly including at the crate level).		2022-02-23 23:41:55 -08:00
..
protos	working_copy: stop keeping track of commit ID	2022-02-12 17:22:37 -08:00
src	build: suppress unstable_name_collisions warnings on stable	2022-02-23 23:41:55 -08:00
tests	build: use assert_matches crate	2022-02-20 22:21:14 -08:00
build.rs	build: conditionally use map_first_last feature if available	2022-02-20 22:21:14 -08:00
Cargo.toml	build: conditionally use map_first_last feature if available	2022-02-20 22:21:14 -08:00