Langium Weekly Dev-Meeting

[msujew]

Hi everyone!

Developers and everyone interested meet every Wednesday at 2 PM UTC (4PM CEST, 10AM EST), to discuss anything related to the development of Langium. If you want to bring up a specific topic at the next meeting, please add it as a comment/edit to the agenda below. We will keep short notes on each topic. Sort the comments below by Newest to stay up to date on the latest dev-meeting notes.

Google Meet

The dev-meeting will be held using google meet:

https://meet.google.com/bcm-iqtq-egm

Community Calendar

An open calendar is available to include the dev meeting and other relevant events in your personal or business calendar:

https://calendar.google.com/calendar/u/0?cid=Y19rbGJlbnJnbW5vMWkwbG1uM3FzdDAwZzI3Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t

[msujew]

Agenda 29/06/2022

• [@msujew] Discuss roadmap (See result here Roadmap Q3 2022 #573)
• [@spoenemann] Website showcase is ready to review now: Statemachine browser showcase langium-website#52
• [@gfontorbe] Refactoring the References service to be used by all relevant LSP services
• [@montymxb] Discussion on whether inferred types are allowed to extend declared types

[msujew]

Agenda 06/07/2022

• [@spoenemann] Enable type resolution across files (Interface defines in a Langium file isn't accessible from another #507)
• [@msujew] Anyone interested in creating a PR for Native Monarch support for Langium #582?

[msujew]

Agenda 13/07/2022

• [@msujew] I've created a (incomplete) list of LSP interfaces that we should support: Support full LSP spec #595
• [@msujew] Anyone up for reviewing Support workspace/executeCommand LSP request #592?

[msujew]

Agenda 20/07/2022

• [@sailingKieler] Roadmap on type inference refactoring
• [@msujew] Continued work on web mode
• [@msujew] Currently looking into refactoring completion, I noticed major issues

[msujew]

Agenda 27/07/2022

[msujew]

Agenda 03/08/2022

• [@pluralia & @sailingKieler] Type inference of non-optional assignment actions
• [@pluralia] Ideas for refactoring the grammar language
• [@msujew] Working on guides for scoping (WIP)

[msujew]

Agenda 10/08/2022

• [@msujew] Completion refactoring has finally finished! Completion service refactoring #623
• [@msujew] Formatting tests Support formatting testing #626

[spoenemann]

Meeting on 17/08/2022 is canceled

None of the current maintainers of Langium are available next Wednesday, so we have to cancel that meeting.

[msujew]

Agenda 24/08/2022

[montymxb]

Agenda 31/08/2022

• [@sailingKieler & @spoenemann ] It would be nice to write up a guide to describe how to create built-in libraries in Langium, related issue
• [@montymxb] Monaco grammar file generation for Langium has been revised again, will give highlighting for Langium in the web.

[goto40]

If you are interested, I could try to provide some minimal examples... If yes: would I place the example or examples in the examples folder of langium or somewhere else? Should we specify the solution first (e.g. a variation of the hello world example with built in persons)?

[snarkipus]

For the uninitiated, what is the use case/utility of built-in libraries? I analyzed your codebase @goto40 but it wasn't immediately obvious to me since I'm unfamiliar with your DSL or its context.

[msujew]

@snarkipus The usual use case would be to declare built-in types that can be referenced by any user of the language without needing to declare them explicitly. One obvious example would be the built-in library of TypeScript, which contains all statically available classes/global variables of JavaScript. The process variable in Node.js for example is exposed that way. We never need to declare it, it's "just there".

[goto40]

As @msujew said: the use case is to provide built-in models, like types (in a language providing types, this could be a default library of default types, line uint32).

A simple example I could try to provide would be the Hello-World-Grammar with some predefined persons. So you could say "Hello MrPredefined1" with some predefined persons (like MrPredefined1). Different ways to provide this predefined models, as sketched by @spoenemann could be assembled in the provided example (or examples)...

[snarkipus]

Thanks @msujew & @goto40 for the explanation! If I've learned anything from this, it's definitely how much functionality modern languages have intelligently baked-in.

[msujew]

Agenda 07/06/2022

[@spoenemann] Performance with large workspaces: how to unload / on-demand-load workspace documents?

• Background: when resolving cross-references, we are already able to load the target document on demand (linker.ts). This capability is currently unused because we keep the whole workspace in memory after initial indexing. An alternative with potentially better performance in terms of initialization time and memory usage would be to only gather exported symbols into the index upon initialization of the language server instead of fully linking and validating all documents, and to unload (remove from memory) the documents and their ASTs afterwards. The big question is what happens when a user loads a document on demand when following a link. That document will be unprocessed, so it won't be possible to navigate references within it.

[msujew]

Agenda 14/09/2022

• [@spoenemann] Langium 0.5 milestone planning. Release is planned at the end of September.
• [@pluralia] Thoughts on Hacktoberfest?

[snarkipus]

@pluralia @msujew I'd be happy to register/participate (as long as the definition of 'pristine' is loose). If you didn't want to 'opt-in' or advertise that Langium is a Hacktoberfest participant, I think you would just need to tag the PRs as HACKTOBERFEST-ACCEPTED.

[pluralia]

@snarkipus, thank you for your attention! I and @montymxb (who initially proposed to participate in Hacktoberfest) discussed issues: there aren't suitable questions in the main repo right now, but adding details to the description of some of them might help. Also, there are suitable issues in other repos under langium organization. We discuss it in tomorrow's Langium Dev-Meeting.

[msujew]

Agenda 21/09/2022

• [@msujew] Release in one week, please review PRs as long as they're hot and fresh :)
• [@pluralia & @montymxb] Hacktoberfest issues

[snarkipus]

@montymxb @pluralia Just following up on Hacktoberfest. Unfortunately, work prevented me from being able to attend today.

[spoenemann]

Agenda 28/09/2022

• [@spoenemann] Release 0.5.0 will be published after the currently assigned PRs are merged.

[pluralia]

Agenda 05/10/2022

• Release 0.5.0 is published 🎉
• [@pluralia] Issues for langium-lox / "roadmap" to implement own DSL
• [@pluralia] Special syntax for infix operators

[snarkipus]

Congratulations on 0.5!

[goto40]

Same from me: congratulations. Thank you for this good work! I noticed that code completion (custom scope providers) works much better now!! In cases where I got many confusion propositions before I get the correct list now. I am very happy with that.

[msujew]

@goto40 Glad to hear that. The completion refactoring had a long time coming (see #623), but I'm also very happy with how the new version performs. There are still some tweaks we need to perform, but it works well for now.

[msujew]

Agenda 17/07/2024

• [@msujew] New patch release probably soon.
• [@JohannesMeierSE] Question about validations on multiple different types of elements.

[msujew]

Agenda 24/07/2024

[msujew]

Agenda 31/07/2024

• [@msujew] TypeFox people (me included) are very busy right now, sorry for the slow PR responses.
• [@Lotes] Looking into improvements of the async parser to improve memory consumption and performance
• [@msujew] Questions about JetBrains plugin for a Langium based language server.
• [@JohannesMeierSE] New improvements to the validation API Extend the API of the validation registry for more performant custom validations #1614.

[msujew]

Agenda 07/08/2024

• [@msujew @aabounegm] [email protected] and [email protected] patch releases have been released.

[msujew]

Agenda 14/08/2024

• [@msujew] Version 3.2 soon(tm) :)

[msujew]

Agenda 21/08/2024

• [@msujew] Discussion around Perform read lock on LSP requests #1640.

[msujew]

Agenda 28/08/2024

• [@msujew @spoenemann] Discussion around Support multi-target references #1509.

[cdietrich]

[cdietrich]

will create an issue

[cdietrich]

#1654

[msujew]

We merged #1600 which might be related to this.

[cdietrich]

problem solved. now calling decode with correct signature

[msujew]

Agenda 04/09/2024

• [@msujew] v3.2.0 update PR ready for review: Update to v3.2.0 #1662 (release candidate has already been approved)

[msujew]

Agenda 18/09/2024

[spoenemann]

Agenda 25/09/2024

• [@spoenemann] We want to do a graduation review to officially leave the incubation phase at the Eclipse Foundation.

Minutes

• [@montymxb] Guest hosting while @msujew is out
• [@aabounegm] PR for hosting Langium's API doc is up & ready for review, API docs #1697, @montymxb will take a look later this week
• [@aabounegm ] Discussed the idea of a potential release schedule (even a soft one) going forward. No decisions were made, but we would like to discuss this a bit in a coming meeting (next week or later)
• [@borisbrodski] has been working on langium-tools to provide a set of helper functions, generator utilities, and testing features (like vitest matchers). He shared the current state, but it's still a WIP, and he's expecting a more complete version in a week or 2.

[msujew]

Agenda 02/10/2024

• [@msujew] Preview release for 3.3 available in the next few days.
• [@Lotes] Utility tooling to better debug the parser.

[msujew]

Agenda 09/10/2024

• [@msujew] Working on a change in Chevrotain to improve lexing performance for function/unicode pattern.

[montymxb]

Agenda 23/10/2024

• [@montymxb ] Most of us are in conferences throughout this week, so we'll catch you all next week!

[msujew]

Agenda 30/10/2024

• [@msujew] Working on major performance optimization, see Support discarding the CST to preserve memory #1733 and feat: optimize unoptimizable token types Chevrotain/chevrotain#2072.

[aabounegm]

Did the meeting time change or was there no meeting today? I joined at 2 p.m UTC but no one was there

[msujew]

Oops, the majority actually met an hour earlier, due to daylight savings taking effect in most of europe. I'll take care to move it to the correct UTC time for next week.

[msujew]

Agenda 06/11/2024

• [@msujew] Daylight savings is messing with people in europe - meeting is happening at 3 PM UTC.
• [@msujew] We plan to make the parser engine more flexible to add antlr4 based parsers to Langium. See also Refactor parsing engine #1742.
• [@msujew] Next weeks meeting will be at 2PM UTC (3PM CET).