λ – Telegram

Finally, I could configure nix development shell with proper LSP support for Go compiler. It was not easy as a beginner nix user. After 4-5 hours researching I decided to see nixpkgs.go_1_25 package and got frustrated from that. Because it was an easy task 😮‍💨

Anyways, I did that! And I am ready to contribute some Go code. Now I am looking through issues page to find easy one to start

https://gist.github.com/abdivasiyev/792939fc4d961b4ad049e7ebb8d8bcf8

52 viewsedited 17:48

Advent Of Code 2025: Day 1

https://github.com/abdivasiyev/aoc-haskell/blob/aada93c69659b71e994248cbae0ecdc1c647fdd4/src/Aoc/Years/Year2025/Day1.hs

GitHub

aoc-haskell/src/Aoc/Years/Year2025/Day1.hs at aada93c69659b71e994248cbae0ecdc1c647fdd4 · abdivasiyev/aoc-haskell

AdventOfCode solutions using Haskell. Contribute to abdivasiyev/aoc-haskell development by creating an account on GitHub.

👍1

50 views16:27

Working in a team is nightmare for an introvert people like me I think. Just I want to work in a quiet without any questions, but it is not possible 😥

51 views11:00

Advent Of Code 2025: Day 2

https://github.com/abdivasiyev/aoc-haskell/blob/master/src/Aoc/Years/Year2025/Day2.hs

GitHub

aoc-haskell/src/Aoc/Years/Year2025/Day2.hs at master · abdivasiyev/aoc-haskell

AdventOfCode solutions using Haskell. Contribute to abdivasiyev/aoc-haskell development by creating an account on GitHub.

50 views12:34

AoC Day 3 Part 2 is so crazy

53 views06:52

https://softwarepatternslexicon.com/haskell/

https://softwarepatternslexicon.com/functional/

Software Patterns Lexicon

Haskell Design Patterns & Pure Functional Architecture

Master Haskell functional programming patterns and architecture—from pure functions, algebraic data types, and typeclasses to monads, applicatives and transformers, lazy evaluation, concurrency, and parallel code—with diagrams, idiomatic Haskell examples…

57 views10:30

A few days ago, I had to use sqlc to generate Go code from sql queries and there was a lack of overriding named parameter types. So I couldn't do anything without it. And after some research I saw sqlc's plugin system and understood how to add my custom overridings. And it was a usefull. Now I am writing only sql queries to generate my repository layer.

https://github.com/abdivasiyev/sqlc-gen-go/commit/c65fe5fa9f63528a46af3cfcc7ec833677bfac46

sqlc.dev

Compile SQL to type-safe code

39 views12:30

now my neck is resting finally

🏆1

43 views18:39

https://whatlang.fun/

whatlang.fun

whatlang — guess the language from a picture

Guess the language from street signs, store names and random inscriptions

40 views13:41

The passkeys are the beauty of security. You just enter your device's password and don't need to pass any password into websites. I don't know it is how secure, but great for users with its UX

47 views16:08

Sometimes I see that a young generation writes a comment for a post like this: where? why? how?

But actually, answers to these questions were written down in the post or an article. I don’t know it is mental issue or a laziness to read something long or something else…

45 views03:47

The usage of pointers so so crazy in Golang.

To find this line, I have spent 2 hours of debugging 🥲.

GitHub

bugfix: parse generic parameterized enum constants by abdivasiyev · Pull Request #2118 · swaggo/swag

Describe the PR
While parsing generic enum types, the parser does not set enums for these types. And due to this, in the generated swagger spec, there are not any enumerations for generic type. Ins...

41 views10:10

Forwarded from Programming Deadlock

Writing your own Cheat Engine in Rust
https://lonami.dev/blog/woce-1/

lonami.dev

Writing our own Cheat Engine: Introduction | Lonami's Blog

First entry on completing Cheat Engine's tutorial without Cheat Engine

32 views03:26

Goroutine leak profiles¶

A new profile type that reports leaked goroutines is now available as an experiment. The new profile type, named goroutineleak in the runtime/pprof package, may be enabled by setting GOEXPERIMENT=goroutineleakprofile at build time. Enabling the experiment also makes the profile available as a net/http/pprof endpoint, /debug/pprof/goroutineleak.

The following example showcases a real-world goroutine leak that can be revealed by the new profile:

type result struct {
    res workResult
    err error
}

func processWorkItems(ws []workItem) ([]workResult, error) {
    // Process work items in parallel, aggregating results in ch.
    ch := make(chan result)
    for _, w := range ws {
        go func() {
            res, err := processWorkItem(w)
            ch <- result{res, err}
        }()
    }

    // Collect the results from ch, or return an error if one is found.
    var results []workResult
    for range len(ws) {
        r := <-ch
        if r.err != nil {
            // This early return may cause goroutine leaks.
            return nil, r.err
        }
        results = append(results, r.res)
    }
    return results, nil
}