Hi, I have certain computations here. I use many parentheses just to make sure computations are all right. How can I write these Julia computations more cleaner? p(x,y,α) = (-(2*α*y-1)^2)/(12*α^2) q(x,y,α) = ((2*α*y-1)^3-(27*α^2)*(x^2))/(108*α^3) del(x,y,α) = (27*α^2*x^4 - 2*(2*α*y-1)^3*x^2)/(…

One approach is to use the let statement to organize intermediate results: q(x,y,α) = let a=2α*y-1, b=3α*x, c=3α (a^3 - 3b^2) / 4c^3 end although it seems like these intermediate expressions appear frequently … do they have names? If so, maybe it’s worth putting them into their own functions.

[image] uniment: q(x,y,α) = let a=2α*y-1, b=3α*x, c=3α (a^3 - 3b^2) / 4c^3 end I have to say I’m not a fan of let blocks, which seem exotic and awkward to me (especially the way they appear above, with the confusing sequence of =s). And the above also appears to me to be a bit of an abuse…

[image] DNF: I have to say I’m not a fan of let blocks, which seem exotic and awkward to me (especially the way they appear above, with the confusing sequence of =s). And the above also appears to me to be a bit of an abuse of shortform function notation, which is really for one-liners. Julia…

Yeah, I love short form too, but mostly for really short functions;) I agree with you that it’s better to split some of these expressions into multiple ones. For example this [image] manya: case1(x,y,α) = ((-(α*y+1)/(3α)) + cbrt((-0.5*q(x,y,α)) + sqrt(del(x,y,α))) + cbrt((-0.5*q(x,y,α)) - sqrt…

Taking a second look, I think the OP’s needs are better served by putting everything in a single function: function r(x, y, α) a, b, c = 2α*y-1, 3α*x, α*y+1 q = (a^3-3b^2)/108α^3 ∇ = x^2*(3b^2-2a^3)/1728α^4 if ∇ ≥ 0 rt∇ = √∇ -c/3α + cbrt(-0.5q + rt∇) + cbrt(-0.5q -…

[image] uniment: -c/3α + cbrt(-0.5q + rt∇) + cbrt(-0.5q - rt∇) I would tend to recommend using explicit return -c/3α + … in multiline functions like this, for clarity.

What’s the point of using , there instead of ;? Seems like the wrong notation

I’ve been avoiding return unless the function terminates early, but I always try different things in the hunt for style. How about return if ∇ ≥ 0...? :wink: I like that it emphasizes that the return value will be found as the result of one of the following branches.

[image] uniment: I’ve been avoiding return unless the function terminates early, but I always try different things in the hunt for style. I think omitting return makes the code harder to read. I see a line in your if statement, and I think “huh, this code does nothing” until I realize that …

Reading these threads, it’s fun to observe the strongly opposed opinions. :laughing: It doesn’t seem to be a settled science, neither in those threads nor in the Julia codebase. From a quick hand-count of functions using longform named function syntax in array.jl (including macros and excluding thi…

Syntax: How to write a cleaner code for many composed computations

New to Julia

stevengj December 30, 2022, 1:56pm 17

I doubt it. The time for purely aesthetic syntactic changes has passed and will never come again. PSA: Julia is not at that stage of development anymore

Topic		Replies	Views
`let` syntax weirdness Internals & Design	38	2352	January 3, 2021
Proposal to extend the syntax of list comprehensions with a `let` clause Internals & Design	38	2349	September 19, 2022
Why does Julia have multiple ways to define functions? New to Julia question	24	2802	October 16, 2024
How should I simplify nested loops? New to Julia question	34	2109	January 23, 2021
Tricks to compile away step in calculation? General Usage	20	1059	November 9, 2023

Syntax: How to write a cleaner code for many composed computations

Related topics