You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
julia>using SampledSignals
julia>SampleBuf([1, 2, 3], 1)
3-frame, 1-channel SampleBuf{Int64, 1}
3.0s sampled at 1.0Hz
███
julia>SampleBuf(1:3, 1)
ERROR: MethodError: no method matching SampleBuf(::UnitRange{Int64}, ::Int64)
Closest candidates are:SampleBuf(::Type, ::Any, ::Quantity) at C:\Users\densb\.julia\packages\SampledSignals\WU1nF\src\SampleBuf.jl:37SampleBuf(::Type, ::Any, ::Quantity, ::Any) at C:\Users\densb\.julia\packages\SampledSignals\WU1nF\src\SampleBuf.jl:38SampleBuf(::Type, ::Any, ::Any...) at C:\Users\densb\.julia\packages\SampledSignals\WU1nF\src\SampleBuf.jl:35...
Stacktrace:
[1] top-level scope
@ REPL[6]:1
This could be fixed by allowing AbstractVector instead of Vector in the constructor. Is there a reason why this has not been done, or should I make a PR?
The text was updated successfully, but these errors were encountered:
I have come to suspect that this issue is a naive take on #60. Are there techincal issues with implementing SampleBuf(1:10, my_samplerate) as valid syntax?
Current behaviour:
This could be fixed by allowing
AbstractVector
instead ofVector
in the constructor. Is there a reason why this has not been done, or should I make a PR?The text was updated successfully, but these errors were encountered: