In the style guide, it talks about type piracy [1], the practice of extending or redefining methods on types you didn’t define. We’ve been told in the past not to do this, especially with methods and types defined by Base, as it can subtly break Julia. However, we are in a situation where we really…

Something like this perhaps? module Nemo export NemoType struct NemoType end Base.exp(::NemoType) = println("calling exp for NemoType") exp(x::Int) = println("calling Nemo.exp for julia type") end resutling in julia> x = NemoType() Nemo.NemoType() julia> exp(x) calling exp for NemoType julia> e…

Clarification on type piracy

General Usage

kristoffer.carlsson September 16, 2017, 7:50pm 3

Having local implementations is not type piracy, see the “extending or redefining” part.

Even more clarification on Type piracy

Topic		Replies	Views
Even more clarification on Type piracy New to Julia package , type , type-piracy	24	3805	January 6, 2022
Julep: Taking multiple dispatch,export,import,binary compilation seriously Internals & Design namespaces	121	8588	May 18, 2018
Minimal working example that demonstrates the danger of type piracy General Usage question , type-piracy	9	1023	August 24, 2021
Is an explicit "export" a good thing? General Usage	51	5813	December 7, 2017
"Meaning", type-piracy, and method merging Internals & Design type-piracy	68	5265	June 3, 2018

Clarification on type piracy

Related topics