You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be my bias but one of the problems I struggled mostly so far while I am trying to learn ruby and write library is the little details how to write library. The issues so far were for example:
What's the proper structure (should lib.rs be in top directory or src//?)
Where test.rs should be (main directory? src//)?
How to build documentation?
What are the policies of annoucement of new libraries?
While some documentation exists it tend to be widespread and sometimes outdated (it might be on third party sites and be say about rust 0.6).
In Linux world there is libabc project which includes a basic sample projects showing how things are supposed to be done. While many details are not applicable to rust it'd be nice to have something like that kept in sync with rust.
The text was updated successfully, but these errors were encountered:
Suppress `question_mark` warning if `question_mark_used` is not allowed
Closesrust-lang#11283
changelog: [`question_mark`]: Don't lint if `question_mark_used` is not allowed
It might be my bias but one of the problems I struggled mostly so far while I am trying to learn ruby and write library is the little details how to write library. The issues so far were for example:
lib.rs
be in top directory orsrc//
?)src//
)?While some documentation exists it tend to be widespread and sometimes outdated (it might be on third party sites and be say about rust 0.6).
In Linux world there is libabc project which includes a basic sample projects showing how things are supposed to be done. While many details are not applicable to rust it'd be nice to have something like that kept in sync with rust.
The text was updated successfully, but these errors were encountered: