@@ -12,12 +12,12 @@ when failures occur. Eliminating these modes of failure in omics development and
12
12
analyses is one of the primary reasons the project was created.
13
13
14
14
To 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** .
16
16
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
21
21
in the unsafe block is expected to operate correctly and not invoke undefined behavior.
22
22
23
23
## Performant
@@ -103,7 +103,7 @@ recommend you dual license the crate to be used under the [MIT
103
103
License] ( https://opensource.org/license/MIT ) or the [ Apache-2.0
104
104
License] ( https://opensource.org/license/apache-2-0 ) at the user's discretion.
105
105
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
107
107
crates) _ must_ be made accessible under any number of the following licenses (in
108
108
alphabetical order):
109
109
@@ -116,22 +116,21 @@ alphabetical order):
116
116
- or any public domain license (e.g.,
117
117
[ Unlicense] ( https://opensource.org/license/unlicense ) ).
118
118
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
122
122
from the list below:
123
123
124
-
125
124
- [ Affero] ( https://www.gnu.org/licenses/agpl-3.0.en.html ) ,
126
125
- [ CDDL] ( https://opensource.org/license/cddl-1-0 ) ,
127
126
- [ GPL] ( https://www.gnu.org/licenses/gpl-3.0.en.html ) ,
128
127
- [ LGPL] ( https://www.gnu.org/licenses/lgpl-3.0.en.html ) ,
129
128
- [ Mozilla Public License 2.0] ( https://www.mozilla.org/en-US/MPL/2.0/ ) .
130
129
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
133
132
the crate is "free for non-commercial use" or other such conditions or restrictions).
134
133
135
134
If any question is not sufficiently covered by the above license reviews, please [ file
136
135
an
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