@@ -12,12 +12,12 @@ when failures occur. Eliminating these modes of failure in omics development and
1212analyses is one of the primary reasons the project was created.
1313
1414To that end, correctness should be considered the highest priority of crates in the
15- ` rust-seq ` stack—** even at the cost of performance** .
15+ ` rust-seq ` stack—** even at the cost of performance** .
1616
17- In situations where performance is critical, developers should provide both a _ safe_
18- and _ unsafe_ interface, clearly documenting the pre-requisites for the _ unsafe_ interface
19- at the API level. Likewise, any ` unsafe ` code should be explicity documented (in the code)
20- with a comment beginning with the token ` SAFETY: ` , that explicitly describes why the code
17+ In situations where performance is critical, developers should provide both a _ safe_
18+ and _ unsafe_ interface, clearly documenting the pre-requisites for the _ unsafe_ interface
19+ at the API level. Likewise, any ` unsafe ` code should be explicity documented (in the code)
20+ with a comment beginning with the token ` SAFETY: ` , that explicitly describes why the code
2121in the unsafe block is expected to operate correctly and not invoke undefined behavior.
2222
2323## Performant
@@ -103,7 +103,7 @@ recommend you dual license the crate to be used under the [MIT
103103License] ( https://opensource.org/license/MIT ) or the [ Apache-2.0
104104License] ( https://opensource.org/license/apache-2-0 ) at the user's discretion.
105105
106- Notably, library crates (i.e. crates that are expected to become dependencies of other
106+ Notably, library crates (i.e. crates that are expected to become dependencies of other
107107crates) _ must_ be made accessible under any number of the following licenses (in
108108alphabetical order):
109109
@@ -116,22 +116,21 @@ alphabetical order):
116116- or any public domain license (e.g.,
117117 [ Unlicense] ( https://opensource.org/license/unlicense ) ).
118118
119- While _ all_ crates are strongly encouraged to adopt a license from the above
120- set, binary crates (i.e. command line applications that are not expected to be a
121- dependency of other crates or tools) _ may_ adopt a stronger copyleft license
119+ While _ all_ crates are strongly encouraged to adopt a license from the above
120+ set, binary crates (i.e. command line applications that are not expected to be a
121+ dependency of other crates or tools) _ may_ adopt a stronger copyleft license
122122from the list below:
123123
124-
125124- [ Affero] ( https://www.gnu.org/licenses/agpl-3.0.en.html ) ,
126125- [ CDDL] ( https://opensource.org/license/cddl-1-0 ) ,
127126- [ GPL] ( https://www.gnu.org/licenses/gpl-3.0.en.html ) ,
128127- [ LGPL] ( https://www.gnu.org/licenses/lgpl-3.0.en.html ) ,
129128- [ Mozilla Public License 2.0] ( https://www.mozilla.org/en-US/MPL/2.0/ ) .
130129
131- Finally, crates (regardless of type) are explicitly _ disallowed_ from using any
132- non-permissive or non-copyleft proprietary license (e.g. any license that stipulates
130+ Finally, crates (regardless of type) are explicitly _ disallowed_ from using any
131+ non-permissive or non-copyleft proprietary license (e.g. any license that stipulates
133132the crate is "free for non-commercial use" or other such conditions or restrictions).
134133
135134If any question is not sufficiently covered by the above license reviews, please [ file
136135an
137- issue] ( https://github.com/rust-seq/docs /issues/new?labels=license&title=license:%20evaluation%20of%20LICENSE ) .
136+ issue] ( https://github.com/rust-seq/rust-seq.github.io /issues/new?labels=license&title=license:%20evaluation%20of%20LICENSE ) .
0 commit comments