bloop VS dotty

https://github.com/BloopAI/bloop Is fully open source and has full text + regex search built on tantivy fyi

Thanks! Bloop really helped with the documentation! they index your code base and uses RAG locally to talk against it. It works shockingly well.

In this blog post, I’ll be comparing 3 distinct AI-first code search tools I recently came across: Cody (developed by late-stage startup, Sourcegraph), SeaGOAT (an open-source project that was trending on HN last week), and Bloop (an early-stage YC startup). I’ll be evaluating them along the dimensions of user-friendliness as well as their accuracy.

If you're confused about any of the code snippets above, you can check out bloop.ai and phind.com (along with its VSCode extension) to answer any of your questions about the repository, noting that both have free plans.

COMPANY: bloop (https://bloop.ai)

bloop (YC S21) | Rust AI Engineer | Onsite | London, UK

We're a YC + tier-1 VC backed startup, working on a AI chat assistant for software developers that can answer questions about any large codebase.

About you: you hack around with GPT on the weekend, maybe you even fine-tune some of these new open source models. But you're also a solid programmer, capable of not just prototyping a nice demo but also shipping performant code that can scale. You're probably quite good at what you do, maybe you were top of your class, or maybe you rose the ranks to your comfortable management role, but yearn for the days of writing code, redbull and deploying on a Friday.

We're a small team, looking for one individual to join us in London, in-person at least 3 days per week.

Please reach out to me at join [at] bloop [dot] ai with "HN AI Engineer" in the subject line and a note about why this is exciting and a link to your portfolio or linkedin/resume.

P.S. Our stack is Rust, so it's likely the role will go to a candidate with Rust experience but if you think you have something to offer that compensates for lack of Rust we should chat anyway!

https://github.com/BloopAI/bloop

Bro let me turn your life inside out: https://bloop.ai

Another example is Bloop, it is a code search engine built on top of tantivy and qdrant.

Bloop is a developer assistant that uses GPT-4 to answer questions about your codebase (https://github.com/BloopAI/bloop)

Dotty? Was it still the name later?

http://dotty.epfl.ch/

I think this might be related to this issue.

You can look (and EPFL collect feedback) about EPFL implementation of async/await: https://github.com/lampepfl/async. Also you can look at dotty ticket about this: https://github.com/lampepfl/dotty/pull/16739

The reason I’m not currently an opaque type user as they do not play well with the tagless final style we use, though I am patiently awaiting some attention on my bug report: https://github.com/lampepfl/dotty/issues/17281

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

Scala Native has much more control on how the Scala AST is compiled, and can easier workaround platform limitations, eg. lazy vals in Scala 3 required reflection config for Native Image (see this and that), while in Scala Native we could mitigate problems with unsupported usage inside in other ways within the compiler plugin.

By the way, you might be interested in this recent PR which overhauls the scala 3 macro docs: https://github.com/lampepfl/dotty/pull/17060.

For example, this issue (https://github.com/lampepfl/dotty/issues/12840) was blocking the migration, it was reported more than a year ago and the fix was finally released a month ago (https://github.com/lampepfl/dotty/releases/tag/3.3.0-RC2).

For the record, there is an implementation of :javap which is close to being done but might need a volunteer to get it over the finish line: https://github.com/lampepfl/dotty/pull/12210

im glad to tell you that in 3.3.0 a lot of these -Wunused lints will be supported: see https://github.com/lampepfl/dotty/pull/16157