-
Notifications
You must be signed in to change notification settings - Fork 992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Style questions #5
Comments
Ok, I see from recent commits there's an effort to standardize on tabbing, so I'll do that. However, I still think using |
Sorry for mixed tabbing, was likely caused to mixing configurations on my end. I've been on the fence about Option and I seem to be on the wrong side of that fence as to what's more or less standard in most Rust libraries. So let's revert to Result<(), Error>. |
Thank you! |
Is there a consistent spacing style we should target for this project? It seems like macros have 2-space tabs, most of the code uses tabs, there is some 4-space tabs, and the dependencies use 4-space tabs (which is standard in the Rust community).
I also don't sit well with
Option<Error>
. The "silly"Result<(), Error>
lets you writeOk(())
which looks funny but has the word "ok" in it. ReceivingNone
and interpreting this as "ok" is confusing at first.I don't want to step on any toes here, but it would be good to agree on these things and have them written down somewhere.
The text was updated successfully, but these errors were encountered: