changeset 156:ef3e6c70b6f9 boundary_conditions

Add missing type parameter to application operator
author Jonatan Werpers <jonatan@werpers.com>
date Mon, 29 Apr 2019 11:40:22 +0200
parents 9fdbae11dd77
children 63b495d5dbc7
files TensorMappings.jl
diffstat 1 files changed, 1 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/TensorMappings.jl	Tue Apr 23 09:54:42 2019 +0200
+++ b/TensorMappings.jl	Mon Apr 29 11:40:22 2019 +0200
@@ -46,14 +46,13 @@
 
 Base.getindex(tm::TensorApplication, I::Vararg) = apply(tm.t, tm.o, I...)
 
-→(t::TensorMapping{R,D}, o::AbstractArray{T,D}) where {T,R,D} = TensorApplication(t,o)
+→(t::TensorMapping{T,R,D}, o::AbstractArray{T,D}) where {T,R,D} = TensorApplication(t,o)
 # Should we overload some other infix binary operator?
 # * has the wrong parsing properties... a*b*c is parsed to (a*b)*c (through a*b*c = *(a,b,c))
 # while a→b→c is parsed as a→(b→c)
 # The associativity of the operators might be fixed somehow... (rfold/lfold?)
 # ∘ also is an option but that has the same problem as * (but is not n-ary) (or is this best used for composition of Mappings?)
 
-
 struct TensorMappingComposition{T,R,K,D} <: TensorMapping{T,R,D}
 	t1::TensorMapping{T,R,K}
 	t2::TensorMapping{T,K,D}