. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 28.16 Thread-safety . . . . . . . . . julia> s2 = "1" "1" julia> pointer.([s1, s2], 1) 2-element Array{Ptr{UInt8},1}: Ptr{UInt8} @0x00000000132c9638 Ptr{UInt8} @0x0000000013dd3d18 julia> s1 = s2 "1" julia> pointer.([s1, s2], 1) 2-element container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 28.16 Thread-safety . . . . . . . . . julia> s2 = "1" "1" julia> pointer.([s1, s2], 1) 2-element Array{Ptr{UInt8},1}: Ptr{UInt8} @0x00000000132c9638 Ptr{UInt8} @0x0000000013dd3d18 julia> s1 = s2 "1" julia> pointer.([s1, s2], 1) 2-element container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 28.16 Thread-safety . . . . . . . . . julia> s2 = "1" "1" julia> pointer.([s1, s2], 1) 2-element Array{Ptr{UInt8},1}: Ptr{UInt8} @0x00000000132c9638 Ptr{UInt8} @0x0000000013dd3d18 julia> s1 = s2 "1" julia> pointer.([s1, s2], 1) 2-element container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 27.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 27.16 Thread-safety . . . . . . . . . julia> s2 = "1" "1" julia> pointer.([s1, s2], 1) 2-element Array{Ptr{UInt8},1}: Ptr{UInt8} @0x00000000132c9638 Ptr{UInt8} @0x0000000013dd3d18 julia> s1 = s2 "1" julia> pointer.([s1, s2], 1) 2-element container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 27.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 27.16 Thread-safety . . . . . . . . . julia> s2 = "1" "1" julia> pointer.([s1, s2], 1) 2-element Array{Ptr{UInt8},1}: Ptr{UInt8} @0x00000000132c9638 Ptr{UInt8} @0x0000000013dd3d18 julia> s1 = s2 "1" julia> pointer.([s1, s2], 1) 2-element container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.16 Thread-safety . . . . . . . . . container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values — the field are distinct types, even though they have identical representations. And of course, all specific pointer types are subtypes of the umbrella Ptr type: julia> Ptr{Float64} <: Ptr true julia> Ptr{Int64}

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 28.16 Thread-safety . . . . . . . . . container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field are distinct types, even though they have identical representations. And of course, all specific pointer types are subtypes of the umbrella Ptr type: julia> Ptr{Float64} <: Ptr true julia> Ptr{Int64}

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.16 Thread-safety . . . . . . . . . container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field are distinct types, even though they have identical representations. And of course, all specific pointer types are subtypes of the umbrella Ptr type: julia> Ptr{Float64} <: Ptr true julia> Ptr{Int64}

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.16 Thread-safety . . . . . . . . . container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field are distinct types, even though they have identical representations. And of course, all specific pointer types are subtypes of the umbrella Ptr type: julia> Ptr{Float64} <: Ptr true julia> Ptr{Int64}

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.15 Accessing Data through a Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 28.16 Thread-safety . . . . . . . . . container that might hold different values over time, and so can only be reliably identified with its address. In contrast, an instance of an immutable type is associated with specific field values –- the field are distinct types, even though they have identical representations. And of course, all specific pointer types are subtypes of the umbrella Ptr type: julia> Ptr{Float64} <: Ptr true julia> Ptr{Int64}