Name this method extension technique, piracy evasion

[mkitti]

@Sukera

I think it’s generally better to try to upstream such additions to an API, instead of wrapping & punning on the name.

Note that I modified the example to remove the export. I definitely do not mean to do this in lieu of upstreaming the example. Some may argue this functionality actually belongs to StructIO.jl though. I actually thought that someone has sumbitted a pull request to write tuples, but I cannot seem to find it at the moment.

Let’s use this scenario though. Let’s say I submit this pull request to JuliaLang/julia. What do I do in the meantime? If I use a different name for the method, then I have to do a search and replace operation once upstream incoprorates and releases it, which could be months or years from now.

[Sukera]

@mkitti

What do I do in the meantime? If I use a different name for the method, then I have to do a search and replace operation once upstream incoprorates and releases it, which could be months or years from now.

That really ought to be something your IDE can easily do for you, no? I’ve used that exact functionality with the LSP numerous times. That’s just regular, every day, plain software engineering.