Why is Go 1.24 disabled for all Go katas (that I tried)?

[Christoph-Harms]

Apart from the fact that 1.24 is already two versions behind and we should be able to code in Go 1.26, I can't find a single kata that will let me submit a Go 1.24 solution. I tried 5 or 6 random katas, and each time, Go 1.24 and Go 1.20 are in the version dropdown, but 1.24 is explicitly greyed out.

I mean, come on, I'm not going to hand-code my slice and map comparisons like it's 1.20 again, I've done that way too often in my life before 1.21.

What's up with this?

[hobovsky]

The problem is that after Golang 1.24 got enabled on the platform, it was made available only for new kata and new golang translations. There is a handful of kata with 1.24 enabled, but there is few of them, and they are not easy to find.

When a language gains a new version, existing kata do not magically gain possibility to use it. To enable new language version for existing kata, such kata has to be either updated manually (forked, changed "version" dropdown, saved, published, and approved), or updated by admins with a tool. Back in the day, when language versions were added, admins bumped up existing kata with an automated script, but, for some reason, it did not happen on last update of languages.

[Christoph-Harms]

Thanks a lot for the quick reply!

Where would be the correct place for me to open an issue requesting to bump up existing kata? My line of reasoning being that there are no and have never been any breaking changes in Go versions, so this shouldn't break even a single kata.

[hobovsky]

Well one possible problem with updates of versions is that it usually implies also update of tooling, dependencies, God knows what else, and even if the language itself promises to be backwards compatible, things sometimes may break in unexpected ways. But I do not say that this is the reason why kata were not updated, because it was really not.

Unfortunately, I am yet to find a way of making requests which would work.

[Christoph-Harms]

Welp, if you find one, let me know. I'd be willing to put some work in, too. Being a Go dev of almost 15 years who is currently unemployed, I have time to spare and (probably hopefully) the appropriate expertise to be able to assist.

[hobovsky]

If you'd be willing to join Codewars Discord server, you could jump into the #fixing channel and maybe we could think of something. In general, amount of required content maintenance is virtually infinite: over 700 kata many of which could use some improvements, over 230 pending Golang translations needing a review, so if you are willing to spend some time on this, a lifetime might be not enough.

[Christoph-Harms]

Bummer, I just deleted my Discord account a few months ago in protest to the whole "age verification" thing (well, and because I didn't use it at all). Since I did this in response to an (in my opinion) immoral/unethical business practice, I'm kind of hesitant to make a new account. I take it this is your main means of communication between the collaborators and there isn't really an alternative?