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
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…
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…
Forwarded from Programming Deadlock
Writing your own Cheat Engine in Rust
https://lonami.dev/blog/woce-1/
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
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:
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
}
λ
The usage of pointers so so crazy in Golang. To find this line, I have spent 2 hours of debugging 🥲.
When you realize your implementation don’t solve anything, just chill and wait someone to solve this issue
😶🌫️😶🌫️😶🌫️
It is because the source actually somehow trash. You can’t understand anything easily
😶🌫️😶🌫️😶🌫️
Adding_a_while_Loop_to_the_Go_124_Compiler_2025_Guide_by_Aleksei.pdf
734.5 KB
Adding a while loop into Go compiler
New year with a new editor.
- Keymaps are learnt
- Plugins are installed
Ready, set, go!
Thanks for challenge to Haskell Uzbekistan
My setup here: https://github.com/abdivasiyev/nix/tree/master/modules/home/emacs
- Keymaps are learnt
- Plugins are installed
Ready, set, go!
Thanks for challenge to Haskell Uzbekistan
My setup here: https://github.com/abdivasiyev/nix/tree/master/modules/home/emacs
👍2
The magit is a real git magic!
I can't believe that, finally I found my best client for git🫡
I can't believe that, finally I found my best client for git🫡
👍2
After writing a few days in a ELisp, I am a master to find an incorrect parentheses with naked eye🤣
😁1