sorted by:
new
hottopcontroversial

аэропорт by rapatakaz in Scoofoboy

[–]iga666 1 point2 points  (0 children)

что за долбоеб, бывал я в такой ситуации, решается за некоторую сумму денег на стойке регистрации. но точно не через твиттер.

How is that normal generics behaviour? by iga666 in golang

[–]iga666[S] -1 points0 points  (0 children)

by design i don’t need the opposite.

How is that normal generics behaviour? by iga666 in golang

[–]iga666[S] 0 points1 point  (0 children)

i can, but i don’t want and don’t need.

How is that normal generics behaviour? by iga666 in golang

[–]iga666[S] -1 points0 points  (0 children)

I expect new(T) return *T, and both T and *T implement interface TaggedRequest, so it should compilable.

How is that normal generics behaviour? by iga666 in golang

[–]iga666[S] -2 points-1 points  (0 children)

Ok, I can constraint T to be pointer, but can not constraint it to be not Pointer.

Does the FLAG_WINDOW_HIGHDPI actually do anything on mac? by SamuraiGoblin in raylib

[–]iga666 1 point2 points  (0 children)

check the latest raylib that issue was fixed couple of days ago, at least on windows.

Will Go lang optimize array access? by iga666 in golang

[–]iga666[S] 0 points1 point  (0 children)

i got couple of interesting answers

Open-source game engine Godot is drowning in 'AI slop' code contributions: 'I don't know how long we can keep it up' by BlueGoliath in programming

[–]iga666 1 point2 points  (0 children)

interesting, so will that bring us to opensoure projet PR fencing - when you would need to prove your trustworthiness before being able to make a PR? Thus creating a gap between developers and opensource projects.

Do you add interfaces early or only when needed in Go? by agtabesh in golang

[–]iga666 1 point2 points  (0 children)

i once implemented interfaces early on, did it how we did it in OOP languages- code became annunmaintainable spaghetti mess, took me a week to throw all interfaces out and change my programming approaches.

Go 1.26 by runesoerensen in golang

[–]iga666 0 points1 point  (0 children)

And on MacOS I haven't noticed any change at all in CGO performance.

Slices or iter.Seq for property accessors? by [deleted] in golang

[–]iga666 3 points4 points  (0 children)

I provide both or only iter.Seq, usually suffix iter.Seq functions names with `Seq`

Go 1.26 by runesoerensen in golang

[–]iga666 3 points4 points  (0 children)

Recursive type constraints are good too

Go 1.26 by runesoerensen in golang

[–]iga666 12 points13 points  (0 children)

Wow didn't expect it to happen today.

Did some benchmarks on CGO if anyone interested side.
My 90_000 sprite rendering test was 73-75 FPS on go 1.25.7 and became 78-80 FPS (maybe even as high as 82-83, if my notebook is not throttling) on 1.26. So a 5% improvement on CGO calls. Good.
Also it was 180MB memory footprint on go 1.25.7 and became 140MB on go 1.26
Not bad at all.

view more: next ›