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 07/02/2024

[msujew]

Agenda 14/02/2024

• [@msujew] The newest release candidate for Langium 3.0 is available as the next version on npm.

[msujew]

Agenda 21/02/2024

[montymxb]

Agenda 06/03/2024

• Langium 3.0 has been released 🥳 ! Check out the blog post to learn more.
• We're collecting user feedback through issues at the moment, but early feedback is looking good
• If you notice something, first check out our discussions & issues, and if it's new feel free to open up a thread.

[pluralia]

Agenda 13/03/2024

• [@montymxb] Experience with Langium 3.0
  • 3.0 has more downloads than any other version
  • [@JohannesMeierSE] Used for one of the client projects -- looks good
• [@pluralia] Issues for external contributors
  • Have no new suitable issues; it might be worth looking at old roadmaps
  • [@montymxb] Host a hackathon where participants propose ideas and implementations using Langium

[montymxb]

Agenda 20/03/2024

• 3.0 release is still looking nice so far (although 3.0: Multi Language cannot handle file renames #1408 needs looking into)
• We should nominate @JohannesMeierSE as a contributor for Langium
• Automation point we should look into regarding the langium-cli, which will save us time on later deployments

[cdietrich]

is the meeting no longer public or has the link secretly changed? we failed to join two times in a row

[spoenemann]

It's probably due to some Google Meet settings; we'll look into it.

[cdietrich]

maybe its set up so that only mark can let people in

[msujew]

I changed the setting so that anyone can join without a join request.

[JohannesMeierSE]

Agenda 27/03/2024

• sprotty-vscode-webview for sprotty 1.1.x or 1.2.x eclipse-sprotty/sprotty-vscode#101 is relevant, but not urgent at the moment
• short discussion about async parsing and workers
• discussed ideas for type checking / Typir:
  • fine-grained traceability for type mismatches as source for meaningful error messages
  • the binding for Langium might provide type information for selected expressions/AstNodes for users as "debugging" information without actual debugging the application

[msujew]

Agenda 03/04/2023

• [@msujew] I'm back from vacation :)
• [@Lotes] Discussion on a new structure for the langium documentation - we should focus on the workflow. More discussion on that next week.
• [@JohannesMeierSE] We should add an adopters page to the Langium website (as in: Who is using Langium for their projects).

[msujew]

Agenda 10/04/2024

• [@cdietrich] Questions about scoping and parser performance.
• [@montymxb] We are soon ready to submit a treesitter grammar to GitHub for syntax highlighting of .langium files.
• [@markus] Presents new structure for the langium documentation: Rearrange documentation and add "learn the workflow" section langium-website#223

[msujew]

Agenda 17/04/2024

• [@cdietrich] Interest in implementing plugin support for the langium-cli (see also Metadata on grammar rules #818).

[msujew]

Agenda 24/04/2024

• [@msujew] I'm currently looking at a few formatter improvement/fixes. Mostly related to Formatter shows cyclic behaviour #1362. Afterwards, it would be a good time to publish a 3.1 of Langium.
• [@JohannesMeierSE] We should finalize the guide on using keywords as identifiers, see Guide how to enable keywords as identifiers #218 langium-website#219.

[msujew]

Agenda 01/05/2024

Cancelled due to public holiday in Germany

[msujew]

Agenda 08/05/2024

• [@msujew] PRs are piling up, please review :)
• [@Lotes] Documentation rewrite is almost ready to be merged.

[msujew]

Agenda 15/05/2024

• [@msujew] Merging a bunch of PRs, v3.1 release probably soon.
• [@JohannesMeierSE] Looking into a possible bug regarding the value conversion of data type rules.
• [@cdietrich] Might contribute some improvements to the sorting of completion item proposals.

[msujew]

Agenda 22/05/2022

• [@msujew] I'm currently working on multi reference support again.