Vojin Jovanovic

Overlap is sometimes perfectly valid. Requiring users to rename their records could be a too big burden. Maybe you can introduce a default scheme for resolving conflicts.

That is a good strategy, if users need it you can always build on top of it. In scala-records we will use the structural types for this.

Yep for renames, although they would be rather nested records. If you merge two records the collided fields would be in the nested record: ``` Rec { lhs: Rec {...

True, I have evaluated the image size and even for an empty main program we get ~5MB of an image. There are a few reasons for that: 1) In our...

[unused-pkgs-hw.txt](https://github.com/oracle/graal/files/1678195/unused-pkgs-hw.txt) [unused-classes-hw.txt](https://github.com/oracle/graal/files/1678198/unused-classes-hw.txt) [unused-methods-hw.txt](https://github.com/oracle/graal/files/1678197/unused-methods-hw.txt) These are the packages, classes, and methods that are never invoked. They can use as an indicator for elements that should not be in the image. Some...

It does, but by looking at the list of included elements, I would not say that GC is the biggest problem. I would rather invest that time to remove things...

It is possible we make a 400 kB "Hello, World!" (@pejovica did this). But this code is completely unsafe and insecure and can lead to segfaults. This could be made...

@jrudolph this is an interesting analysis. `3721664` seems indeed big and we should investigate what takes that much. By looking at the output I would say: 1) `byte[]` takes the...

Thanks for reporting, I will fix the error message and also it would be very useful to have the binaries to see why the instrumentation did not fire. In the...

Nope, it is a `native-image` thing. No need for `mx`, you can use the distributed version as long as your IDE knows where the sources are. If that is hard...