changeset 209:7db145ce6e4d boundary_conditions

Remove comment about @boundscheck causing allocation
author Jonatan Werpers <jonatan@werpers.com>
date Tue, 25 Jun 2019 16:37:35 +0200
parents 992969237359
children 2aa33d0eef90
files LazyTensors/src/lazy_operations.jl
diffstat 1 files changed, 0 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/LazyTensors/src/lazy_operations.jl	Tue Jun 25 11:09:48 2019 +0200
+++ b/LazyTensors/src/lazy_operations.jl	Tue Jun 25 16:37:35 2019 +0200
@@ -54,9 +54,6 @@
     b::T2
 
     @inline function LazyElementwiseOperation{T,D,Op}(a::T1,b::T2) where {T,D,Op, T1<:AbstractArray{T,D}, T2<:AbstractArray{T,D}}
-        # NOTE: Seems like adding the boundscheck introduces allocations. Can this
-        # be fixed? Since boundscheck is removed when inlined into inbounds this
-        # should not in practise effect performance.
         @boundscheck if size(a) != size(b)
             throw(DimensionMismatch("dimensions must match"))
         end