Hi All, Wanted to flag a Julia cheat-sheet I recently stumbled across that seems phenomenally concise and comprehensive! Open for PRs if anyone wants to contribute more! EDIT: This was rolled into JuliaDocs org, so updated url in link above to The Fast Track to Julia

would be nice with a print-friendly version

[image] kristoffer.carlsson: Passing by value is a fairly standard term. See for example: language agnostic - What's the difference between passing by reference vs. passing by value? - Stack Overflow . Two points: We could continue reading SO answer: “However, if the value in question is a m…

My point is that there is no difference how arguments are passed to functions. It just happens that some object are mutable and some are not. Hence, I don’t think the statement about argument passing need to be there at all.

I agree with this, nevertheless it is apparent that some newcomers to Julia struggle with the semantics of shared structure, so an opportunity to point it out should not be wasted. Possibly a “cheat sheet” is not the right place to expand on this, but it could contain a link to tutorials .

Regarding pass by value, the question is: is passing an argument x to a function parameter p equivalent to assignment p=x? The answer, in Julia, is yes, so it is pass by value. (If x is a mutable object, the of course its contents can still be altered via p.) If you’ve never used a true pass-by-re…

[image] kristoffer.carlsson: Immutable types are passed around by value (i.e. copying), whereas mutable types are passed by reference. I’m not sure this is really true. Since you can’t modify an immutable struct it doesn’t matter if you copy it or not to pass it as an argument, and the compiler…

@kristoffer.carlsson and @Elrod : OK, think I addressed most of these in this PR . Few followups: [image] kristoffer.carlsson: Free up memory for large arrays with arr = nothing That’s not true in interactive programming, unfortunately, which I know some of us still use. [image] kristoffe…

[image] nickeubank: I think it means that import will load all functions defined in a module, while using only imports the exported functions. Tried to clarify. No - see the section in the manual about the differences between import and using: https://docs.julialang.org/en/latest/manual/faq/…

[image] ScottPJones: No - see the section in the manual about the differences between import and using: https://docs.julialang.org/en/latest/manual/faq/#What-is-the-difference-between-“using”-and-“import”?-1 ah, ok thanks! Will revert.

The cheat sheet has been moved to the JuliaDocs org now, so the URL changed to The Fast Track to Julia It would probably be nice to update the link in the OP as well, in case someone stumbles onto this thread in the future.

Excellent cheat-sheet

Community

nickeubank December 16, 2017, 7:44pm 21

[Edit: got correct quote this time]

Happy to change, but I’ll confess I’m a little confused, as this is what’s in the Julia official docs:

Topic		Replies	Views
How to explain these two statements? General Usage question	11	815	August 13, 2018
Understanding generated assembly for simple loop Performance llvm	14	6177	March 19, 2018
Error missing about side-effect on immutable type General Usage	11	781	January 20, 2020
Why I can't set what parameters are mutable explicitly? Offtopic functions	170	6686	August 23, 2022
Mutable vs immutable struct: modifying an array field General Usage struct , mutable-structure	4	1935	February 22, 2023

Excellent cheat-sheet

Related topics