The issue in this post has come up a few times in different contexts: [image] Stheno marginals Probabilistic programming I’m trying to follow the examples but having some issues. What’s going wrong here? [8188c328] Stheno v0.7.1 # # This file just shows how some of the b…

[image] cscherrer: The potential benefits are pretty clear If I understand right, we’re talking about merging two functions with different semantics into the same function object? Could you explain what you see as the benefits of doing that?

[image] cscherrer: In any case, it’s hard to imagine a time when ever use of every name complies neatly with some widely-used API. The challenge is how to make things easily interoperable even when this isn’t the case. If they are not describing the same generic concept then they should not b…

Sorry to interfere, but it seems that discussion has deviated from the original post. If I am getting it right, than problem is not in the API or meanings, but in the fact that module A export foo struct A1 end foo(x::A1) = "hello" end module B export foo struct A2 end foo…

[image] jzr: Could you explain what you see as the benefits of doing that? Say we have two packages that export a foo function. using both of them forces the name to be qualified. The problem is similar to type piracy: importing one package changes the behavior of another. We mostly have two…

[image] cscherrer: users to only use using with specific names. This is a good idea in general since it enhances readability. It’s a bit annoying to type, but IDE tooling can help by automatically inserting using Foo: bar, baz statements names at the top of a file. [image] cscherrer: I t…

To solve the issue of having to manually import names, there is this julia-vscode issue: https://github.com/julia-vscode/julia-vscode/issues/1925

[image] jzr: This is a good idea in general since it enhances readability. It’s a bit annoying to type, but IDE tooling can help by automatically inserting using Foo: bar, baz statements names at the top of a file. I think it depends on the context. Some packages are designed to be used inter…

[image] cscherrer: With apologies to @cpfiffer and @devmotion , here’s an example from AbstractMCMC.jl : :rofl:

"Names" packages?

Tooling

Tamas_Papp April 13, 2021, 7:19am 18

This is not a problem, it is a feature that protects the user/programmer. The two names denote different things, and should not be automatically conflated. See this epic thread:

Topic		Replies	Views
Function name conflict: ADL / function merging? Internals & Design proposal , namespaces	212	15263	April 30, 2018
Julep: Taking multiple dispatch,export,import,binary compilation seriously Internals & Design namespaces	121	9224	May 18, 2018
Reserving names in Base Internals & Design	26	1701	June 4, 2018
Opinions for exporting common names General Usage namespaces	29	1551	July 23, 2021
Package naming guidelines Community	57	5410	January 11, 2026

"Names" packages?

Related topics