Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps and single segment namespace #58

Closed
Hendekagon opened this issue Oct 4, 2024 · 4 comments
Closed

deps and single segment namespace #58

Hendekagon opened this issue Oct 4, 2024 · 4 comments
Assignees

Comments

@Hendekagon
Copy link

Please could you add a deps.edn and prefix the clj-uuid namespace because single segment namespaces cause warnings and are incompatible with GraalVM

@dco-lentz dco-lentz self-assigned this Oct 4, 2024
@dco-lentz
Copy link
Collaborator

sure thing I added deps.edn as a todo to #57

As far as single segment namespace -- I'd be concerned to just break backward compatibility do you have an example of an existing single-segment-name project that has accommodated GraalVM in a clean way?

@Hendekagon
Copy link
Author

hi, thanks. The problem with SSNs is described here, perhaps for backwards compatibility the approach taken here would work

@dco-lentz
Copy link
Collaborator

Ok, I've deprecated the single-segment clj-uuid namespace and transitioned this to clj-uuid.core over on 0.2.1-SNAPSHOT branch #56. Please let me know how this works for you.

@dco-lentz
Copy link
Collaborator

Incorporated deps.edn and transitioned clj-uuid -> clj-uuid.core and deployed as clj-uuid 0.2.1-SNAPSNOT as part of ongoing work toward 0.2.1 release PR #56

Lets move discussion over to that branch or the associated Issue #57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants