typesanitizer

12 ms·

1.
by typesanitizer 7d ago
> [..] so isolation isn't a WHERE clause somebody has to remember, [..] Two things the post doesn't cover and I'm happy to get into. What closing the cross-region lost update actually took: [..] Set of my Claude alarm bell
2.
by typesanitizer 2mo ago
Go compiles things at package-level granularity. You only need to recompile your reverse dependencies on making changes. Also there's build caching available out-of-the-box, as well as some support for test caching.
3.
Computer Says No: Error Reporting for LTL(wickstrom.tech)
5 points by typesanitizer 11mo ago|0 comments
4.
by typesanitizer 2y ago
I have removed the mention of "Let it crash" from that section, and added a clarification for my original intent. I did not mean it as criticism of Erlang or Joe Armstrong, although I 100% understand how it could've been inte
5.
by typesanitizer 2y ago
Hi Gavin, I've seen your blog before, including some posts about Yao. After feedback on Lobste.rs, I plan on adding a section on conditions and restarts, hopefully sometime later today if time permits. :) I'd be happy to add some
6.
by typesanitizer 2y ago
Hi, blog post author here (unrelated to paper authors). > So in a laps of 15 years (2010-1025), The paper was published in 2014, so the period is 2010-2014, not 2010-2025. > they hand picked 20 bugs from 5 open source filesystem proje
7.
by typesanitizer 2y ago
Hi, author here. I'm a big fan of Armstrong's work, I've watched several of his talks multiple times and always get something new out of them even if I don't agree entirely. :) I do mention Erlang near the start of the p
8.
by typesanitizer 2y ago
Copying my comment from the Lobste.rs thread ( https://lobste.rs/s/az2qlz/epic_treatise_on_error_models_for... ) > Hi, author here, the title also does say “for systems programming languages” :) > For continua
9.
by typesanitizer 2y ago
Thanks for writing the summary notes and sharing those here. After reading the Usenix article, I was thinking that we could apply some of the ideas at $WORK, but the exact "How" was still not super clear. Your notes offer a compac
10.
by typesanitizer 2y ago
> If you have any language where it is "semantially correct" to execute it with a simple interpetter, than all optimizations in that language are not semantically important by definition, right? Technically, yes. :) But I think
11.
by typesanitizer 2y ago
> In my view, if a compiler optimization is so critical that users rely on it reliably “hitting” then what you really want is for that optimization to be something guaranteed by the language using syntax or types. The way tail calls work
12.
by typesanitizer 2y ago
I'm guessing you've tried these flags mentioned in the blog post but haven't had luck with them? > LLVM supports an interesting feature called Optimization Remarks – these remarks track whether an optimization was performe
13.
by typesanitizer 2y ago
I've added a clarification in the post to make my position explicit: > This is not to imply that we should get rid of SQL or get rid of query planning entirely. Rather, more explicit planning would be an additional tool in database
14.
by typesanitizer 2y ago
Thanks for the feedback. The preceding paragraph had "and occasionally language features" so I thought it would be understood that I didn't mean it as an optimizer-specific thing, but on re-reading the post, I totally see how
15.
by typesanitizer 2y ago
Structured concurrency is part of the Swift standard library, and was added at the same time when first-class support for concurrency was added. TaskGroup in the standard library - https://developer.apple.com/documentation&#
16.
by typesanitizer 3y ago
Based on your use of "campaign" (the older name for Batch Changes), it sounds like you were looking into Sourcegraph about 2.5 years ago or before that. Lots has changed since then. We recently released a new indexer scip-clang (
17.
by typesanitizer 3y ago
I don't know the answer to your original question, but based on this StackOverflow answer ( https://stackoverflow.com/a/60564952/2682729 ), it seems like a small compiler wrapper should do the trick to get the
18.
by typesanitizer 4y ago
All of our SCIP indexers are open-source: scip-java (for Java, Kotlin and Scala), scip-typescript (for TypeScript and JavaScript), scip-python, scip-ruby, scip-go and scip-clang (for C and C++). There are also some community-maintained OSS
19.
by typesanitizer 4y ago
(I work on C++ indexing at Sourcegraph.) As my colleague mentioned in a sibling comment, we have an existing indexer lsif-clang which supports C++. I just added a Chromium example to the lsif-clang README right now: (direct link) https:&#x
20.
by typesanitizer 4y ago
Fixed, thanks.
21.
by typesanitizer 4y ago
For C++, we do support Bazel via compile_commands.json; we have customers who have used it successfully. Depending on the editor you're using, you probably need to get Bazel to generate a compile_commands.json anyways. So core code nav
22.
by typesanitizer 4y ago
Created a PR to mention tools using SCIP in the README. https://github.com/sourcegraph/scip/pull/101
23.
by typesanitizer 4y ago
I don't think this is entirely accurate. For example, the Translation Validation section on this Wikipedia page mentions ( https://en.wikipedia.org/wiki/Compiler_correctness ) > Translation validation can be used
24.
by typesanitizer 4y ago
Hey! I work on code intelligence at Sourcegraph, so I figured I'd chime in here. > why don't you have decent crossrefs We do have compiler-accurate cross references for many repos. Some examples: - TypeScript: https:/&#x2
25.
by typesanitizer 4y ago
I sympathize with your point that being able to use simpler tools (such as grep) is often a good thing instead of having to rely on heavy-duty functionality (such as a full IDE/language server). That said: - Ctrl+F in a file specifical
26.
by typesanitizer 4y ago
Ah, making it non-exported was an unintentional mistake. I've pushed a fix marking it as exported with an EDIT note.
27.
by typesanitizer 4y ago
> There's no perfect language, yet people are always trying to find one. It's OK if you don't like Go and prefer another language, the real devil / tradeoff is in the fact that conformance to a single language (or set
28.
by typesanitizer 4y ago
> Some complaints also seem like a lack of experience using the language. > In my experience, the two-value (explicit capacity) form of "make" is significantly _less_ common than the single-value form. Indeed, gripping thro
29.
by typesanitizer 4y ago
> I would be curious to know what he thought of Swift (having worked on the compiler). The language seems to be the opposite of Go in including every language feature under the sun. Are you asking from a language design perspective? Or
30.
by typesanitizer 4y ago
I didn't mention it because I didn't run into date handling code myself over the past 6 months. I've focused on the positives and negatives that I've run into in practice.

More ›