Re: [go-nuts] Go without garbage collector

[Robert Engels]

I won't dispute that, but at least this particular case, it requires on-going maintenance by the developer (company). In this case of Java very few performance improvements have required code changes.

Using a different structure entirely (hash map vs. tree map) is a different issue - it touches on the robustness of the stdlib, dynamic runtime class replacement, etc. I can only assume that std::map was used because it made the code easier/portable to write in C++ rather than adding an outside dependency or custom hash map. implementation (In the Java code, they use a custom IntegerSet, IntegerList to avoid boxing...)

-----Original Message-----
From: ⚛ <0xe2.0x9a.0...@gmail.com>
Sent: Feb 13, 2020 9:57 AM
To: golang-nuts
Subject: Re: [go-nuts] Go without garbage collector

On Thursday, February 13, 2020 at 3:05:45 PM UTC+1, Robert Engels wrote:

The code hasn’t been changed. The performance numbers have changed dramatically with no developer intervention. No “hand optimizing” required.

C++ evolves over time also. Hashmaps have been added to C++ in C++11, which from today's viewpoint invalidates most benchmarks published before year 2011 that translated Java's HashMap to C++'s std::map.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f5a4a3cf-e4ce-4fb4-af03-fa5f32a5ce62%40googlegroups.com.

-- 

You received this message because you are subscribed to the Google Groups "golang-nuts" group.

To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1149226989.3184.1581615195727%40wamui-sophie.atl.sa.earthlink.net.