HN user
For me, the difference is that if methods are inlined, the compiler is still required to do a copy for structs but not for value classes.
I do not know how this is called.
I think pass by copy is a consequence of being modifiable.
The other solution is to stack allocate and pass a pointer but as i said, unlike in C#, i do not think it's possible to do that in Java.
In Go, you can stack allocate but when you send a pointer (that escapes), the compiler will heap allocate the object.
The article has a section about that.
For me, a struct in C/C# can be modified and is passed by copy while a value class can not be modified and is passed by value.
I do not think you can do stack allocation in Java.
The usual GC tradeoff is between memory and CPU performance. If you set the memory max high, the GC will run less often, you get less pause time.
So I do not understand why it's a surprise that minimizing the pause time requires more memory. Is it because there is no knob to set either the max pause time or the max memory ?
I agree. And the next section is very clear that they want to kill the project.
> For example, rather than proposing one single concrete JIT implementation,
> it may make more sense for the PEP to describe a JIT infrastructure that
> can support multiple implementation strategies.
> Since many different and promising JIT tracing approaches continue to be proposed,
> we believe the infrastructure should make it easy to experiment with and evaluate
> those approaches within CPython rather than be highly coupled with a single strategy.
You need more than that for the example with setTimeout(). It requires to be able to freeze the stack and then go back later.
You need stackful coroutine (like goroutine) for that.
If you do not block 3rd party harness, people will discover that a good harness is more important than a good model.
Yes, and let's not forget Stephen Elop's 'Burning Platform' Memo
Parser generators are great in Python (Lark for me) so you can iterate fast and get a runtime spec of your grammar.
A hand-written recursive descent parser is something you do later when you start to industrialize your code, to get better error messages, make the parser incremental, etc.
Bison/ANTLR are code generators, they do not fit well in that model.
In C#, all instances have a class, so there is already a discriminant, the class itself.
In the article, the example with the switch works because it switches on the class of the instance.
In Scala 3, the inline keyword is part of the macro system.
When inline is used on a parameter, it instructs the compiler to inline the expression at the call site. If the expression is substantial, this creates considerable work for the JIT compiler.
Requesting inlining at the compiler level (as opposed to letting the JIT handle it) is risky unless you can guarantee that a later compiler phase will simplify the inlined code.
There's an important behavioral difference between Scala 2 and 3: in 2, @inline was merely a suggestion to the compiler, whereas in 3, the compiler unconditionally applies the inline keyword. Consequently, directly replacing @inline with inline when migrating from 2 to 3 is a mistake.
There is a modern equivalent based on Linux criu.
Yes, the version in Java is clearly less elegant. Java has map+lambda and compareTo (<=>) but no tuple assignemnt and no splat.
record AppVersion(int major, int minor, int patch) implements Comparable<AppVersion> {
public static AppVersion of(String version) {
var array = Arrays.copyOf(Arrays.stream(version.split("\\.")).mapToInt(Integer::parseInt).toArray(), 3);
return new AppVersion(array[0], array[1], array[2]);
}
public int compareTo(AppVersion other) {
return Comparator.comparingInt(AppVersion::major)
.thenComparingInt(AppVersion::minor)
.thenComparingInt(AppVersion::patch)
.compare(this, other);
}
public String toString() {
return "%d.%d.%d".formatted(major, minor, patch);
}
}For the record (sorry), I believe C# uses the clone operation because records support inheritance.
For me, this is where lies the design flaw, trying to support both inheritance and be immutability at the same time.
Libya was bombed primarily by France and then other NATO countries for no good reason
https://en.wikipedia.org/wiki/Alleged_Libyan_financing_in_th...
And AISQL is a thing ...
https://quickstarts.snowflake.com/guide/getting-started-with-cortex-aisql/index.html
Java Almanac has a list of all features https://javaalmanac.io/features/
And the main page let you compare API versions https://javaalmanac.io/
at least I know that the phone will be supported for at least 4 years
It's 4 (mid) to 7 years (flagship) for Samsung.
https://www.androidauthority.com/samsung-android-updates-114...
OOP is great for libraries but leads to overly complex codes for applications.
For a long time, Java was like, every classes is a library, i do not think it's a failure of OOP, it's a failure of Java.
But I'm optimistic, I choose to see recent additions like records and pattern matching has a step in the right direction.
I've just tried to change a field of an instance of a record using reflection, and it's not possible, even with setAccessible(true).
In Java, constants are declared as static final.
static final Complex CONSTANT = new Complex(1, 2);
static final StableValue<Complex> STABLE_VALUE = StableValue.of();
Complex getLazyConstant() {
return STABLE_VALUE.orElseGet(() -> new Complex(1, 2))
}
In JavaScript, a 'let' inside the initializer of a for loop is captured by value, all the others are captured by reference.
I think it's fair to call that semantics "implicit".
Parroting something i have heard at a Java conference several years ago, tail recursion remove stack frames but the security model is based on stack frames, so it has to be a JVM optimization, not a compiler optimization.
I've no idea if this fact still holds when the security manager will be removed.
I'm sympathetic to the points being made but the argument that Oracle does not have its own JavaScript runtime does not hold. An OracleBD is able to execute triggers written in JavaScript since quite some time.
see https://blogs.oracle.com/java/post/multilingual-engine-execu...
Is their a design document, somewhere about this new library ?
The jep does not explain how to prepare to new Java bytecodes and future enhancements. Am i suppose to only run with the latest version of Java if i want to use that library ?
the default is trivial, it just returns the object's address
This was trivial a long time ago. Now, all Java GCs move objects in memory.
Very true, in Java, at least in the last 20 years, inheritance is de-facto deprecated, all new bits and bolts like enums, annotations, lambdas or records do not support inheritance.
So you have to use composition.
COBOL changes very slowly, once in a decade or two. Python does not offer support of a release for more than 3 years and a half [1].
I'm using Java Almanac [1].
BTW, Saint Louis is the common name of Louis IX not Louis XIV (the Sun King).