Hi Tony,
I've only been using Lint for two days, so I might be doing it wrong, but
I'm getting a lot of false positives about values I've declared, but not
used - upon closer inspection of my code, they are almost always used,
sometimes within loops, sometimes in if/else branches, sometimes as
arguments when constructing a function within a function. Is there a limit
to where Lint can detect whether I'm using a variable or not?
Futher, I'm sometimes getting UndefVarErrors when I use functions from
packages (such as pdf from distributions, or PyPlot), even when the
packages are loaded. Any way to get around this?
Also, I'm often getting Errors about my type constraints, but I'm sure this
is related to my limited understanding of how this works. An example:
function f{T<:Float64}(x1::T, x2::T, x3::Array) will give me "Error:
Float64 is a leaf type. As a type constraint it makes no sense in
T<:Float64". I thought this was a way of efficiently expressing that both
x1 and x2 should be of type Float64, but apparently that's not a great idea?
In any case it's a great package that has already helped me catch quite a
few significant mistakes in my code, so thanks a lot for your work!
Best,
Nils
