|
2 | 2 |
|
3 | 3 | > **<sup>Syntax</sup>**\
|
4 | 4 | > _Crate_ :\
|
5 |
| -> UTF8BOM<sup>?</sup>\ |
6 | 5 | > SHEBANG<sup>?</sup>\
|
7 | 6 | > [_InnerAttribute_]<sup>\*</sup>\
|
8 | 7 | > [_Item_]<sup>\*</sup>
|
9 | 8 |
|
10 | 9 | > **<sup>Lexer</sup>**\
|
11 |
| -> UTF8BOM : `\uFEFF`\ |
12 | 10 | > SHEBANG : `#!` \~`\n`<sup>\+</sup>[†](#shebang)
|
13 | 11 |
|
14 | 12 |
|
@@ -65,19 +63,13 @@ apply to the crate as a whole.
|
65 | 63 | #![warn(non_camel_case_types)]
|
66 | 64 | ```
|
67 | 65 |
|
68 |
| -## Byte order mark |
69 |
| - |
70 |
| -The optional [_UTF8 byte order mark_] (UTF8BOM production) indicates that the |
71 |
| -file is encoded in UTF8. It can only occur at the beginning of the file and |
72 |
| -is ignored by the compiler. |
73 |
| - |
74 | 66 | ## Shebang
|
75 | 67 |
|
76 | 68 | A source file can have a [_shebang_] (SHEBANG production), which indicates
|
77 | 69 | to the operating system what program to use to execute this file. It serves
|
78 | 70 | essentially to treat the source file as an executable script. The shebang
|
79 |
| -can only occur at the beginning of the file (but after the optional |
80 |
| -_UTF8BOM_). It is ignored by the compiler. For example: |
| 71 | +can only occur at the beginning of the file. |
| 72 | +It is ignored by the compiler. For example: |
81 | 73 |
|
82 | 74 | <!-- ignore: tests don't like shebang -->
|
83 | 75 | ```rust,ignore
|
@@ -162,7 +154,6 @@ or `_` (U+005F) characters.
|
162 | 154 | [_Item_]: items.md
|
163 | 155 | [_MetaNameValueStr_]: attributes.md#meta-item-attribute-syntax
|
164 | 156 | [_shebang_]: https://en.wikipedia.org/wiki/Shebang_(Unix)
|
165 |
| -[_utf8 byte order mark_]: https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8 |
166 | 157 | [`ExitCode`]: ../std/process/struct.ExitCode.html
|
167 | 158 | [`Infallible`]: ../std/convert/enum.Infallible.html
|
168 | 159 | [`Termination`]: ../std/process/trait.Termination.html
|
|
0 commit comments