ABOUT UNWRAP() unwrap() is basically an assert that declares that some given error = invariant/corrupt data. that's it brotha. however, most of the time, errors aren’t invariants, they’re just data you should propagate with ? or handle without panicking. some errors truly do

do people test products before shipping?

I'm building this in the-editor fuck it

oh yes

there are 2 things I need to do in order for the editor to actually be the main thing I use: - file watching: "rla" is a very shitty command and I hate it, this is the most complicated and I'm still thinking about it. - Taelin 's workflow of select + call agent. this idea

yes I agree please support The Institute for Type Safe Memetic Research

jesus fucking christ convex is so good wtf

so we're dropping new models every week with some extra % to them, I see

FILE WATCHING FINALLY!! that was honestly not that hard at all. file watching runs a single filesentry::Watcher across the workspace, dispatches FileSystemDidChange events (these are defined within the-editor), and a hook enqueues reload jobs that the main loop drains to update

this is very good advice. LSP is a great tool if implemented properly, but there's a lot of value in you not depending on completions. you can also grep definitions/references very easily for things inside your codebase, so goto def doesn't add that much value here, but it does

fucking hell this is getting good I'm very thankful that OpenCode has a builtin ACP module btw

I be moving like prime all might these days

yes I've built the second acceptable text editor in history (first one is helix)

I want to build first class support for jujutsu as VCS provider in the-editor. do yall have any ideas on jujutsu features for a text editor?

wtf 500 followers I love you all

I feel like I'm being kidnapped and forced to use nix at this point. HSVSphere where's cab mf