joomy

6K posts

joomy banner
joomy

joomy

@joomy

researcher @Bloomberg. 📜 somehow a computer doctor. tweets about formal verification, compilers, types, metaprogramming, linguistics. 🇹🇷

New York City Katılım Şubat 2010
966 Takip Edilen3.9K Takipçiler
Sabitlenmiş Tweet
joomy
joomy@joomy·
can't find a topic for your next programming languages paper? worry not! type system idea generator: type.systems
English
6
67
201
0
Omar Rizwan
Omar Rizwan@rsnous·
saw @joomy talk about his Turkish-like morphosyntactic programming language github.com/kip-dili/kip where arguments can go in any order (because inflection, not word order, carries the meaning) & reminded me of @tobyshooters on geometric code layout (critique of code formatters)
Omar Rizwan tweet media
cristóbal@tobyshooters

@pelavarre @rsnous The secret is that this whole endeavor is just me trying to find geometric code layout that dies when you use a formatter. 4.1 was where I started!

English
2
1
8
1.3K
joomy
joomy@joomy·
traveling to San Francisco tomorrow for IEEE S&P (and to give a keynote at the LangSec Workshop). 🌉 any mutuals in the area wanna hang out Wednesday evening?
English
3
0
13
1.2K
joomy retweetledi
pastaya
pastaya@realpastaya·
GUYS THE C++30 STANDARD LEAKED
pastaya tweet media
English
114
285
3.8K
170.5K
joomy
joomy@joomy·
@kirancodes Lean has GHC or SYB style Generics? my impression was that that kind of generics does not mesh well with dependent types.
English
1
0
2
177
joomy
joomy@joomy·
@weston_mcn my objection here is rather to the word "abstraction".
English
0
0
0
24
joomy
joomy@joomy·
my C++ surprise of today: you thought smart pointers would solve your memory management problems? it turns out, if you have a recursive data structure, and a big enough instance of it, the default destructor can cause a stack overflow! (so you need a custom iterative destructor)
English
22
10
268
26.1K
Trusted
Trusted@trustednstaller·
@joomy I never understood how anyone could ever buy the zero-cost abstraction motto. Of course there's always a cost. The only questions are about when it matters and when they can be justified.
English
1
0
0
41
joomy
joomy@joomy·
@ssh4net both unique_ptr and shared_ptr are susceptible to this problem.
English
1
0
1
295
joomy
joomy@joomy·
@ALX23uz `head = std::move(head->next);` is the problem, not linked lists in general, it seems?
English
1
0
0
705
Dellort
Dellort@ALX23uz·
@joomy Also, a unique pointer technically causes UB in a linked implementation. I recall the cppreference's example of correct usage of unique pointer for a linked list had a UB
English
1
0
0
795
Joseph Garvin
Joseph Garvin@joseph_h_garvin·
@joomy This shouldn't happen for most recursive data structures because they're almost always trees so you should only need O(lg(n)) stack frames. If you're running into this you must be using a linked list? In which case it's more idiomatic to have 1 class for the list as a whole.
English
1
0
8
1.5K
Peter0x44
Peter0x44@peter0x44·
@joomy Or just increase your stack size? In any case, this has never happened to me. And I feel you probably should rethink your strategy anyway...
English
1
0
1
878
Guillaume Claret 🐻‍❄️
Guillaume Claret 🐻‍❄️@guillaumeclaret·
A difficulty with formal methods is that it can mean many things, from fuzzing (some people consider it to be) to full interactive theorem provers, and even there there are differences. This is still a gold mine in terms of security.
Charenton-le-Pont, France 🇫🇷 English
2
0
4
302
andrew blinn
andrew blinn@disconcision·
age of maxislopism is nigh
andrew blinn tweet media
English
5
6
161
13.4K