hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus length(s) <= lastindex(s) String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the

hex literals for integer values, one typically is using them to represent a fixed numeric byte sequence, rather than just an integer value. Binary and octal literals are also supported: julia> x = 0b10 through the indices 1 through lastindex(s) and index into s, the sequence of characters returned when errors aren't thrown is the sequence of characters comprising the string s. Thus we have the identity String. In such situations a rule is that when parsing a sequence of code units from left to right characters are formed by the longest sequence of 8-bit code units that matches the start of one of the