SnoopCompile's limitation is that it only collects data for calls that have not been previously inferred, so you must perform this type of analysis in a fresh session. ![]() JET integrates with SnoopCompile, and you can sometimes use SnoopCompile to collect the data to perform more comprehensive analyses. Consequently, a report of No errors detected does not imply that your entire codebase is free of errors. However, if the argument-types for a call cannot be inferred, JET does not analyze the callee. JET explores the functions you call directly as well as their inferrable callees. virtualized the context of Main (took 0.004 sec) ![]() update and save the demo.jl), JET will automatically re-trigger analysis, and this time, won't complain anything: # demo # = # fibonacci # - fib(n) = n ≤ 2 ? n : fib(n - 1) + fib(n - 2)įib( 1000) # never terminates in ordinal execution fib(m) # undef var fib( "1000 ") # obvious type error # language features # - # user-defined types, macros struct Ty(($(vals.),)) )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |