rovingeye

5 ms·

1.
by rovingeye 8mo ago
it's literally the exact same thing. We use trailing return types to be consistent across the language.
2.
by rovingeye 8mo ago
This has been valid C++ since C++ 11
3.
by rovingeye 9mo ago
It looks like you missed the part where you "move the context into the lambda body via capture specifier."
4.
by rovingeye 9mo ago
Consistency (lambdas, etc.)
5.
by rovingeye 9mo ago
All my window classes uses cbWndExtra, and I leave GWLP_USERDATA for the user who is creating windows.
6.
by rovingeye 9mo ago
That doesn't sound like a valid wndproc
7.
by rovingeye 9mo ago
I assume by "move the context into the body" you mean using GetWindowLongPtr? Why not just use a static wndproc at that point?
8.
by rovingeye 9mo ago
I wasn't aware of the thread local trick, I solve this problem by not setting WS_VISIBLE and calling SetWindowPos & ShowWindow after CreateWindow returns (this solves some other problems as well..)
9.
by rovingeye 11mo ago
I have that turned on in Windows Terminal but still use ctrl+c because it's how all other software works
10.
by rovingeye 11mo ago
The windowing is pretty broken if you use system scaling https://github.com/zed-industries/zed/issues/40272
11.
by rovingeye 1y ago
Thanks for the info. Looks like they're using /silent right there in the example "Steam customers love a quick and silent install. Add silent or quiet parameters to all run process commands and only add what you absolutely ne
12.
by rovingeye 1y ago
MicrosoftEdgeWebview2Setup.exe /silent /install
13.
by rovingeye 1y ago
I can understand the argument, since npm has no solution for TypeScript packages, unlike JSR: "You publish TypeScript source, and JSR handles generating API docs, .d.ts files, and transpiling your code for cross-runtime compatibility.&
14.
by rovingeye 1y ago
I can sort of understand the publishing argument, since npm doesn't solve for this at all, unlike JSR: "You publish TypeScript source, and JSR handles generating API docs, .d.ts files, and transpiling your code for cross-runtime c
15.
by rovingeye 1y ago
I mean, you can just use a loader, as we've all been doing. It's already built, they just didn't implement it properly.
16.
by rovingeye 1y ago
What? All this does is strip types
17.
by rovingeye 1y ago
Why would I want to ship a JS build for my private package? That's just extra machinery I don't need. Switching to a superior runtime would be easier.
18.
by rovingeye 1y ago
I made the same comment here https://news.ycombinator.com/item?id=44931575 "To discourage package authors from publishing packages written in TypeScript" I tried to use it with private packages but that doesn&#x27
19.
by rovingeye 1y ago
It was the first thing I tried and of course it didn't work. It might finally be time to switch to Deno or Bun =(
20.
by rovingeye 1y ago
https://github.com/nodejs/node/issues/57215 Not supporting type stripping in node_modules is unfortunate
21.
by rovingeye 2y ago
Win32 + WebView2
22.
by rovingeye 2y ago
That's about when they added the capability, yeah. They've dropped support for win 7/8, not sure if CHOC goes back that far. I suppose this would break the "Nothing needs adding to your build system to use any of this st
23.
by rovingeye 2y ago
I still don't see a reason to re-implement this functionality when you can just.. statically link the loader. CHOC is great though!
24.
by rovingeye 2y ago
Yeah, it's kind of silly when the WebView2 loader can be statically linked. It's just build system avoidance. CHOC is great though!
25.
by rovingeye 3y ago
Users want an installer. You can see what the installers are doing by looking at the scripts in the repo (this is an open source project). Admin permission is necessary to write to the Global VST folder. You can direct your "Wow"