Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

launching a clojure program, refs #140#141

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
hiredman wants to merge4 commits intoclojure:master
base:master
Choose a base branch
Loading
fromhiredman:patch-4

Conversation

hiredman
Copy link
Contributor

No description provided.

@puredanger
Copy link
Member

I think this is long enough that it should move into its own guide on Deploying Clojure Apps (I'm sure there's more that could be added).

@hiredman
Copy link
ContributorAuthor

the bit about-m taking a var is incorrect, I was confusing clojure's behavior there with lein's

christoph-frick, iku000888, and whilo reacted with thumbs up emoji

@@ -192,4 +192,3 @@ Example:
Because of its focus on immutable data, there is generally not a high value placed on data encapsulation. Because data is immutable, there is no need to worry about someone else modifying a value. Likewise, because Clojure data is designed to be manipulated directly, there is significant value in providing direct access to data, rather than wrapping it in APIs.

All Clojure vars are globally available so again there is not much in the way of encapsulation of functions within namespaces. However, the ability to mark vars private (either using `defn-` for functions or `def` with `^:private` for values) is a convenience for a developer to indicate which parts of an API should be considered public for use vs part of the implementation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Can you remove this errant change?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I merged master into this branch, and I don't think this is an issue anymore

Copy link
Member

@puredangerpuredanger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Generally I think what's here is good, but would like to also include pointers/links into what this means for the popular tools like clj, lein, boot, etc.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@puredangerpuredangerpuredanger requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@hiredman@puredanger

[8]ページ先頭

©2009-2025 Movatter.jp