hell yeah, writing docs

#programming #dlang

@soulsource it’s worse than that. Non-destructive moves, while definitely an improvement on the semantic horror of auto_ptr, force us to have objects with an “empty” state, repeating the billion dollar mistake again and again… Rust is so much better in that respect that it isn’t funny

Self-referential legacy objects could probably even have been made movable by introducing something akin to D’s post-blit operator (but for moves)

#cplusplus #rust #dlang

Juan Vazquez and Cameron Cunning rejoin the show to discuss how we fared with the 2025 Advent of Code competition.

#rust #elixirlang #dlang #Aoc2025 #AdventOfCode #programming

https://straypointers.com/e/s4e01.htm

S4:E01 - 2025 Advent of Code Follow-Up - The Stray Pointers Podcast

S4:E01 - 2025 Advent of Code Follow-Up - The Stray Pointers Podcast

D言語の更新まとめ 2026年1月版(dmd 2.112.0) - Qiita

はじめに D言語の公式コンパイラである dmd が更新され、最新バージョンである 2.112.0 が 2026/01/07 にリリースされました。 今回もmacOSのRegression騒ぎやらで色々あったようで、前回リリースの 2.111.0 からかなりの時間を要しまし...

Qiita

So thinking about asyncronous programming again and how I probably need to ditch #dlang's GC if I want performance and then it hit me:

Why tf is std.socket.Socket an heap-allocated, gc'd class to begin with?!?!

It dosn't uses syncronized that would require a classes monitor, nor does it hold any significant amount of data.

  • a socket_t (fancy 32-bit fd)
  • a ushort-enum for the address family (16-bit)
  • and an bool under windows, which in an asyncronous context we could remove since all will always be non-blocking

So in sum it holds 48-bit of data, while an pointer on modern systems will always be 64-bit (classes are always pointers / by ref in dlang).

Sure, it "uses" inheritance for 2 wrapper types TCPSocket and UDPSocket, which dont actually do anything other than pre-filling the type/protocol arguments in the constructor, which dont even survive after the call to socket(2)...

Is the std really that badly engineered at times or am I going crazy???

#dlang #programming #development #async #networking #garbagecollector

1.26次元の図形?! ~フラクタル図形の次元を計算してみる~ - Qiita

序 本記事はTRIAL&RetailAI Advent Calendar 202517日目の記事です。 昨日の記事は @tech_tuna さんのマグネットポンプをつかって自動灌水機をつくりたかったです。 家庭菜園の水やりを自動化したい!ということで試行錯誤されていました...

Qiita

Currently working (again) on my async framework in #dlang

I need to say coming back to #dlang after a extensive while of #rust coding, I do miss a lot of features of rust already (tho it's nice for once not fighting against the borrow checker or some strange tokio bugs), like choice-types, pattern matching and traits.

Tho it's nice to just have an decent gc and not the need of wrapping everything in `Arc<RefCell<Box<T>>>` /s

Got plenty of ideas for my async framework after working with tokio (and reading parts of it and mio).

#coding #programming #development #async #eventdriven

GitHub - jimlawless/aoc2025: Advent of Code 2025

Advent of Code 2025. Contribute to jimlawless/aoc2025 development by creating an account on GitHub.

GitHub
aoc2025/day_01 at main · jimlawless/aoc2025

Advent of Code 2025. Contribute to jimlawless/aoc2025 development by creating an account on GitHub.

GitHub
2025年 D言語まとめ - Qiita

はじめに 2025年も気がつけば年の瀬です。世間では生成AIのモデル競争やコーディングエージェントなどの実用化が熱いらしいですが、その少し横ではD言語コミュニティも相変わらず地道に前進を続けています。 あ、ほとんどのエージェントはD言語書けますからその点は安心してください...

Qiita