Binary Caching and Pre-compilation .. again

[jpsamaroo]

And for anyone who would like some “context” on this proposal and related discussions, here was everything I could find:

Julep: Taking multiple dispatch,export,import,binary compilation seriously

I want to formalize a julep for a design idea, I am asking the help of the community , please read and criticise freely. The problems it is addressing: Type piracy: It is too easy to break code in module M, even without directly evaluating code into it, by adding methods to Base functions or any other modules that module M depends upon. exmaple: import Base: + +(a::Float64,B::Float64) = 0.0 sum(rand(5)) 0.00 Conflicting names: if both module M and module N export the same function name f …

MultiFunctions: Context dispatch and binary cache

I have been writing this draft for several days , and got a little mixed up verbalising these ideas , which are simpler to understand using code and examples… If you want to jump straight into code, there is a link at the end. @Jameson @mbauman tl;dr There is a way to make Julia completely binary cacheable(between sessions), so it can become an effective way of developing and distributing .so .dll Background Function = a module wide constant symbol ( e.g :sum) without any specifications re…

"Meaning", type-piracy, and method merging

The meaning of “meaning” A common theme that comes up when discussing type-piracy/method merging, etc. is that there “can only be one meaning” for a given function without namespace qualifications (I am being careful there to say function, not method). I just want to get some clarification from the developers on this, because clarity in communication would help for educating users, deciding what macros are reasonable, and what can be discouraged. (Of course, part of this is driven by the fact…

Save actual machine code in precompile files