Julia v1.9.4 Documentation
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition can yield, meaning multiple concurrent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 1644 页 | 5.27 MB | 1 年前3Julia 1.9.3 Documentation
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition can yield, meaning multiple concurrent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 1644 页 | 5.27 MB | 1 年前3Julia 1.9.2 Documentation
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition can yield, meaning multiple concurrent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 1644 页 | 5.27 MB | 1 年前3julia 1.13.0 DEV
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition yield, meaning multiple concur- rent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 2058 页 | 7.45 MB | 3 月前3Julia 1.12.0 RC1
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition yield, meaning multiple concur- rent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 2057 页 | 7.44 MB | 3 月前3Julia 1.12.0 Beta4
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition yield, meaning multiple concur- rent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 2057 页 | 7.44 MB | 3 月前3Julia 1.12.0 Beta3
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition yield, meaning multiple concur- rent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 2057 页 | 7.44 MB | 3 月前3julia 1.12.0 beta1
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition yield, meaning multiple concur- rent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 2047 页 | 7.41 MB | 3 月前3julia 1.10.10
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition can yield, meaning multiple concurrent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 1692 页 | 6.34 MB | 3 月前3Julia 1.10.9
bring x and y to a common type: f(x::T, y::T) where {T} = ... f(x, y) = f(promote(x, y)...) One risk with this design is the possibility that if there is no suitable promotion method converting x and For a more general way to make all such calls work sensibly, see Conversion and Promotion. At the risk of spoiling the suspense, we can reveal here that all it takes is the following outer method definition can yield, meaning multiple concurrent tasks may use the same buffer on a given thread, introducing risk of data races. Further, when more than one thread is available tasks may change thread at yield points0 码力 | 1692 页 | 6.34 MB | 3 月前3
共 86 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9