├── LICENSE-MIT ├── .github └── ISSUE_TEMPLATE │ └── meeting_proposal.md ├── README.md ├── fcps.md ├── meetings.md ├── CODE_OF_CONDUCT.md └── LICENSE-APACHE /LICENSE-MIT: -------------------------------------------------------------------------------- 1 | Permission is hereby granted, free of charge, to any 2 | person obtaining a copy of this software and associated 3 | documentation files (the "Software"), to deal in the 4 | Software without restriction, including without 5 | limitation the rights to use, copy, modify, merge, 6 | publish, distribute, sublicense, and/or sell copies of 7 | the Software, and to permit persons to whom the Software 8 | is furnished to do so, subject to the following 9 | conditions: 10 | 11 | The above copyright notice and this permission notice 12 | shall be included in all copies or substantial portions 13 | of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF 16 | ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 17 | TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 18 | PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 19 | SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY 20 | CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 21 | OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR 22 | IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 23 | DEALINGS IN THE SOFTWARE. -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/meeting_proposal.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Meeting Proposal 3 | about: Propose a topic for a team meeting 4 | title: "(My meeting proposal)" 5 | labels: meeting-proposal 6 | assignees: '' 7 | 8 | --- 9 | 10 | # Summary 11 | 12 | XXX: Briefly describe what this meeting is about. What are the questions you're hoping to get 13 | answered or at least make progress on? If it's non-obvious, why is this topic relevant to T-opsem? 14 | 15 | ## Reading 16 | 17 | XXX: Provide some links to any prior discussions or documents on this topic. If attendees are 18 | expected to read any of these before the meeting, indicate that. If you plan on writing a document 19 | to drive the meeting, indicate that here too. 20 | 21 | # Comment policy 22 | 23 | These issues are meant to be used as an "announcements channel" regarding the proposal, and not as a 24 | place to discuss the technical details. Feel free to subscribe to updates. We'll post comments when 25 | reviewing the proposal in meetings or making a scheduling decision. In the meantime, if you have 26 | questions or ideas, ping the proposers on [Zulip] (or elsewhere). 27 | 28 | [Zulip]: https://github.com/rust-lang/compiler-team/blob/master/content/about/chat-platform.md 29 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # opsem-team 2 | 3 | Home of the operational semantics team. 4 | 5 | The opsem team is the successor of the unsafe-code-guidelines working group and responsible for 6 | answering many of the difficult questions about the semantics of unsafe Rust. It is also a subteam 7 | of the [lang team][lang-team]. For more information about the team, see the [RFC][rfc] in which it 8 | was created. For an up-to-date list of members, see the [governance section of the 9 | website][members]. 10 | 11 | [lang-team]: https://github.com/rust-lang/lang-team 12 | [rfc]: https://rust-lang.github.io/rfcs/3346-t-opsem.html 13 | [members]: https://www.rust-lang.org/governance/teams/lang#Operational%20Semantics%20team 14 | 15 | This repo is used primarily for procedural items like meeting proposals. For technical discussions 16 | around unsafe code, see the [unsafe code guidelines repo][ucg-repo] instead. 17 | 18 | [ucg-repo]: https://github.com/rust-lang/unsafe-code-guidelines 19 | 20 | ### Chat 21 | 22 | Outside of the UCG repo, much of the team's discussion happens [in the `#t-opsem` stream on Zulip][zulip]. 23 | 24 | [zulip]: https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem 25 | 26 | ### Meetings 27 | 28 | The team holds weekly meetings. For details around scheduling and format and the 29 | calendar of future meetings, see the [dedicated page](meetings.md). 30 | 31 | ### FCPs 32 | 33 | If you want to get an idea of which decisions have already been made, [here is a list of FCPs](fcps.md). 34 | 35 | ## Code of Conduct and licensing 36 | 37 | All interactions on this repository (whether on issues, PRs, or 38 | elsewhere) are governed by the [Rust Code of 39 | Conduct](CODE_OF_CONDUCT.md). 40 | 41 | Further, all content on this repository is subject to the standard 42 | [Rust](LICENSE-MIT) [licensing](LICENSE-APACHE). 43 | -------------------------------------------------------------------------------- /fcps.md: -------------------------------------------------------------------------------- 1 | ## FCPs 2 | 3 | Here we track all the FCPs of the team. These reflect consensus decisions and 4 | are thus a useful starting point for figuring out what is (and is not) 5 | guaranteed. 6 | 7 | - Stack-allocated 8-aligned objects are insufficiently aligned by MSCV on x86-32. 8 | [That is indeed UB when such pointers flow to Rust.](https://github.com/rust-lang/rust/issues/112480#issuecomment-1606326864) 9 | - The validity invariant of integers, floats, bool, thin raw pointers, and char is [as documented here](https://github.com/rust-lang/unsafe-code-guidelines/issues/439). 10 | - The validity invariant of function pointers is [as documented here](https://github.com/rust-lang/unsafe-code-guidelines/issues/440). 11 | - Typed copies [reset all padding bytes to uninitialized memory](https://github.com/rust-lang/unsafe-code-guidelines/issues/301#issuecomment-1661617803). 12 | - Layout [cannot change at runtime](https://github.com/rust-lang/unsafe-code-guidelines/issues/97). 13 | - Unsafe code gets to [assume that `size == stride` in arrays](https://github.com/rust-lang/unsafe-code-guidelines/issues/176). 14 | - The `*` projection (value-to-place conversion) itself is never UB; 15 | instead, inbounds/alignment checks get [deferred to later during place evaluation](https://github.com/rust-lang/reference/pull/1387). 16 | - `_` patterns in `match` [do not read from the place, they only require place construction itself to succeed without UB](https://github.com/rust-lang/rust/pull/103208#issuecomment-1735947916). 17 | - Atomic loads [can work on read-only memory, but only under some conditions](https://github.com/rust-lang/rust/pull/115577#issuecomment-1731284113). 18 | - Zero-sized memory accesses and offsets [are NOPs](https://github.com/rust-lang/unsafe-code-guidelines/issues/472) 19 | - The validity invariant of [slice wide pointer metadata are defined here](https://github.com/rust-lang/unsafe-code-guidelines/issues/510). 20 | - [Int-to-pointer transmutation is questionable.](https://github.com/rust-lang/rust/pull/122379#issuecomment-1994699439) 21 | - [Redundant StorageDead/StorageLive are legal.](https://github.com/rust-lang/rust/issues/99160#issuecomment-2155924538) 22 | - [`size_of_val` is safe to call on slice-tailed unsized types with a dynamic slice length of 0.](https://github.com/rust-lang/rust/pull/126152#issuecomment-2220159220) 23 | 24 | Also see [this automatically maintained list](https://github.com/search?q=org%3Arust-lang+label%3At-opsem+label%3Afinished-final-comment-period%2Cfinal-comment-period&type=pullrequests), 25 | which however might not be fully accurate. 26 | -------------------------------------------------------------------------------- /meetings.md: -------------------------------------------------------------------------------- 1 | ## Meetings 2 | 3 | Team meetings are currently held every Tuesday at noon, Boston time. You can see what time that is 4 | in your timezone [here](https://everytimezone.com/s/53a200c0). The meetings take place on jitsi: 5 | . 6 | 7 | On the third Tuesday of every month we skip our regular meeting in exchange for asynchronous 8 | planning. During this time, we pick meeting topics for the upcoming timeslots from our pool of open 9 | [meeting proposals]. Upcoming meetings are listed below. 10 | 11 | [meeting proposals]: https://github.com/rust-lang/opsem-team/issues?q=is%3Aissue+is%3Aopen+label%3Ameeting-proposal 12 | 13 | Anyone with a topic that they would like to see covered should feel free to [file a 14 | proposal][meeting template]. 15 | 16 | [meeting template]: https://github.com/rust-lang/opsem-team/issues/new?assignees=&labels=meeting-proposal&template=meeting_proposal.md&title=%28My+meeting+proposal%29 17 | 18 | Meetings will typically have a champion - someone responsible for driving the meeting and preparing 19 | any design documents to read. This person will typically be the same person that wrote the proposal 20 | (although that is not a hard requirement). Additionally, someone will be given the responsibility of 21 | taking notes. 22 | 23 | 24 | #### Upcoming Meetings 25 | 26 | * 2023-10-10: UCG Backlog Bonanza 27 | * 2023-10-03: UCG Backlog Bonanza (or no meeting due to expected low attendance) 28 | * 2023-09-26: Behavior of `_` in match patterns. [Issue](https://github.com/rust-lang/opsem-team/issues/16) 29 | 30 | #### Past Meetings 31 | 32 | * 2023-09-12: Do `Vec` and `Box` have an aliasing requirement? [Issue](https://github.com/rust-lang/opsem-team/issues/14) 33 | * 2023-09-05: UCG backlog bonanza 34 | * 2023-08-29: Do we allow zero-sized memory accesses? [Issue](https://github.com/rust-lang/opsem-team/issues/12) 35 | * 2023-08-22: When accessing a field that is at a "very aligned" offset, can the required alignment be higher than the type of the field indicates? [Issue](https://github.com/rust-lang/opsem-team/issues/11) 36 | * 2023-08-08: UCG Backlog Bonanza 37 | * 2023-08-01: UCG Backlog Bonanza 38 | * 2023-07-25: UCG Backlog Bonanza 39 | * 2023-07-11: Documentation and resources for unsafe code. [Issue](https://github.com/rust-lang/opsem-team/issues/4) 40 | * 2023-07-04: Valid uses of addr_of! (and requirements of places). [Issue](https://github.com/rust-lang/opsem-team/issues/9) 41 | * 2023-06-27: inbounds requirements. [Issue](https://github.com/rust-lang/opsem-team/issues/10) 42 | * 2023-06-13: UCG Backlog Bonanza 43 | * 2023-06-06: UCG Backlog Bonanza 44 | * 2023-05-30: Spec validation. [Issue](https://github.com/rust-lang/opsem-team/issues/7). [Minutes](https://hackmd.io/ty4NFkQfQjunJn_qTowOtw). 45 | * Champion: Jakob 46 | * 2023-05-23: UCG Backlog Bonanza. [Minutes](https://hackmd.io/@2S4Crel_Q9OwC_vamlwXmw/HyUe4w5rh/edit). 47 | * Champion: Jakob 48 | * 2023-05-09: Match & UnsafeCell. [Issue](https://github.com/rust-lang/opsem-team/issues/5). [Minutes](https://hackmd.io/@wSaA8OrrSQ2SlegMvA6e6A/By6wL4mNh/edit). 49 | * Champion: Connor 50 | * 2023-05-02: Generator optimizations. [Issue](https://github.com/rust-lang/opsem-team/issues/3). [Minutes](https://hackmd.io/@2S4Crel_Q9OwC_vamlwXmw/SJYzJNi72). 51 | * Champion: Jakob 52 | * 2023-04-25: UCG Backlog Bonanza. [Minutes](https://hackmd.io/@2S4Crel_Q9OwC_vamlwXmw/ByeNxbHXh). 53 | * Champion: Jakob 54 | * 2023-04-18: Initial planning. [Minutes](https://hackmd.io/qNSeMDDGTTGMki1qzDEurA). 55 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # The Rust Code of Conduct 2 | 3 | A version of this document [can be found online](https://www.rust-lang.org/conduct.html). 4 | 5 | ## Conduct 6 | 7 | **Contact**: [rust-mods@rust-lang.org](mailto:rust-mods@rust-lang.org) 8 | 9 | * We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic. 10 | * On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all. 11 | * Please be kind and courteous. There's no need to be mean or rude. 12 | * Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer. 13 | * Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works. 14 | * We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the Citizen Code of Conduct; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups. 15 | * Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Rust moderation team][mod_team] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back. 16 | * Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome. 17 | 18 | ## Moderation 19 | 20 | 21 | These are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Rust moderation team][mod_team]. 22 | 23 | 1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.) 24 | 2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed. 25 | 3. Moderators will first respond to such remarks with a warning. 26 | 4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off. 27 | 5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded. 28 | 6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology. 29 | 7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed. 30 | 8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others. 31 | 32 | In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely. 33 | 34 | And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust. 35 | 36 | The enforcement policies listed above apply to all official Rust venues; including official IRC channels (#rust, #rust-internals, #rust-tools, #rust-libs, #rustc, #rust-beginners, #rust-docs, #rust-community, #rust-lang, and #cargo); GitHub repositories under rust-lang, rust-lang-nursery, and rust-lang-deprecated; and all forums under rust-lang.org (users.rust-lang.org, internals.rust-lang.org). For other projects adopting the Rust Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion. 37 | 38 | *Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).* 39 | 40 | [mod_team]: https://www.rust-lang.org/team.html#Moderation-team 41 | -------------------------------------------------------------------------------- /LICENSE-APACHE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. --------------------------------------------------------------------------------