Proposal: Reduce namespace pollution by unexporting identifiers (breaking change) #13
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
kahliburke/Kaimon.jl#13
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description:
Kaimoncurrently exports a large number of identifiers. In particular,start!andstop!have a very high probability of colliding with other packages or user-defined functions.As I understand the typical workflow,
Kaimonis imported alongside the package being developed, but the user rarely needs to callKaimonfunctions directly after the initial setup ("set it and forget it").Suggestions:
public)I recognize this is a breaking change. However, since the package is not yet registered and has no downstream dependencies, it shouldn't be a problem.
@Eben60 Thanks for the feedback on this, I'll take a look at what can be removed from exports.
Implemented in
d615d78on the1.1branch.Only
Gate,@mcp_tool, andMCPToolare now exported. Everything else is declaredpublic— accessible asKaimon.foo()but not imported byusing Kaimon.This eliminates the
start!/stop!collisions and keeps the namespace clean. Docs updated to use qualified references.