Consider moving schema boilerplate from examples to a binary crate

[uint]

In contracts, we have a tradition of keeping schema.rs in examples/. Since schema.rs is not an example at all (it generates an important build artifact!), it's a confusing layout and probably not the proper place for this code.

With very minimal changes, it's possible to move examples/schema.rs to src/bin/schema.rs and have it work pretty much the same - with cargo schema or cargo run --bin schema generating the schemas.

What do you think?

[hashedone]

I was thinking about it at some point and I don't think I found any reason not to. I guess that the initial reason why it put in examples was that it requires less setup - literally: no setup, while as binary you have to play around with Cargo.toml and you may not want to read this doc for POC, and then you leave it. I have the same issue with check_contract binary except it bothers me way more there as I really want to install it on my machine with cargo install and installing it with --example seems off and strange (not a problem for me, but it is how it might be seen from the outside).

[uint]

while as binary you have to play around with Cargo.toml

I thought so too, but actually I tested this today and Rust autodetects the binary crate if it's in /src/bin. There's pretty much no extra setup compared to examples/schema.rs.

[uint]

I have the same issue with check_contract binary except it bothers me way more there as I really want to install it on my machine with cargo install and installing it with --example seems off and strange (not a problem for me, but it is how it might be seen from the outside).

I didn't even realize it's an example! Huh. I agree.

[uint]

@hashedone I opened a ticket for the check_contract issue: CosmWasm/cosmwasm#1371. It bothers me too now 😁