That does fix everything, but I was hoping to find something that doesn't rely on manual checks of VERSION.
At any rate, I didn't have any other problematic case for this stuff, so now that you've fixed Lint I'll just return to my observer status. On Thu, Jun 25, 2015 at 2:00 PM, Tony Fong <tony.hf.f...@gmail.com> wrote: > I have just put out an update to the Lint.jl master which should have some > examples of what you need. Hopefully this would fix the tuple length issue > for you. > > > On Wednesday, June 24, 2015 at 2:54:03 PM UTC-4, Josh Langsfeld wrote: >> >> Thanks, Matt. I hope your stuff does eventually make it into Base. So if >> I'm not mistaken, there is currently no way to get tuple type code that is >> cross-compatible between 0.3 and 0.4 without doing your own mini Compat >> code that looks at VERSION? >> >> If that's the case, what would would think about putting that check into >> your package and making Tuples.length, etc... work for both? I'm currently >> taking a look at submitting an upgrade PR to Lint.jl and this sort of stuff >> is all over. >> >> On Wednesday, June 24, 2015 at 2:22:14 PM UTC-4, Matt Bauman wrote: >>> >>> Right now there's not an official way to do this. You could take a look >>> at my Tuples package[1], which is an attempt at hashing out the API before >>> trying to get this functionality into base. Your feedback would be very >>> welcome! >>> >>> 1: https://github.com/mbauman/Tuples.jl >>> >>> On Wednesday, June 24, 2015 at 1:14:41 PM UTC-4, Josh Langsfeld wrote: >>>> >>>> What is the correct way to get the number of types inside of a T = >>>> Tuple{...} type? Is there anything better than length(T.types), which might >>>> be compatible with the 0.3 style ( >>>> (T1,T2,T3,...))? >>>> >>>
