I wonder what the devs and community think of the direction of context dispatch as it has been recently presented in other various posts.

What do you mean by “context dispatch” ?

It would be great if you could at least link the relevant posts, or ideally write up a coherent, detailed proposal. Reviewing something scattered over “various posts” is not ideal.

If you meant ‘contextual dispatch’, this is what allows you to override existing functions in the context of GPU processing. So it has its applications. @context GPU @contextual(GPU) sin(x::Float32) = ccall((:__nv_sinf, :libdevice), Cfloat, (Cfloat,) x)

Hi, sorry, for reference here is the latest discussion we had on this. [image] Proposal for SharedFunctions.jl package for optional dependency management Internals & Design There are three several topics here as I see it and I’ll do my best to be brief and concise, with a…

The answer should be yes, or in some case you cannot extension things at all. If you re-extension some already existing methods, you do type piracy. However, something to achieve the functionalities(of new extension for some argument type) might be a hard demand, which comes up with a requirement a…

If you’re referring to the ability to “safely” add dispatches that would normally be considered type piracy, then the widely-understood “contextual dispatch” (aka Cassette or IRTools) is exactly what you want. The real issue with regular type piracy is that it can cause unexpected behavior by just l…

Would you mind briefly reiterating what your form of “contextual dispatch” implies? The sharing of this term with what Cassette-like packages implement makes things rather confusing (maybe you can come up with an alternative term for it?). Some things I’d like to have explicitly stated include: Ho…

It is very similar to ”Context Dispatch” of cassette but is aimed to be implemented on the language level. It would help solve a few current pain points of the language.

[image] Proposal for SharedFunctions.jl package for optional dependency management The building blocks: A Context is a set of modules. The Context of module M is the set of all modules that module M depends upon. Extension: The method table for a Context consists only from methods belonging to …

[image] StefanKarpinski: This seems like it requires a new version of sort! to be compiled not only for each type signature (roughly what we currently do), but also for each type signature and for each calling context since the method tables of all functions that are called are different in diff…

Discussion: Context Dispatch - yes? no? questions? answers?

Internals & Design

TsurHerman May 14, 2019, 1:05pm 5

Hi, sorry, for reference here is the latest discussion we had on this.

Topic		Replies	Views
Proposal for SharedFunctions.jl package for optional dependency management Internals & Design	74	6462	May 7, 2019
MultiFunctions: Context dispatch and binary cache Internals & Design proposal , scope	9	2430	July 16, 2018
Julep: Taking multiple dispatch,export,import,binary compilation seriously Internals & Design namespaces	120	9753	May 18, 2018
"Meaning", type-piracy, and method merging Internals & Design type-piracy	67	5933	June 3, 2018
Binary Caching and Pre-compilation .. again Internals & Design precompilation	7	3703	July 22, 2022

Discussion: Context Dispatch - yes? no? questions? answers?

Related topics