From 0db2c14b3d95e947e2b512737b347db46ab674cd Mon Sep 17 00:00:00 2001 From: Antonio Nuno Monteiro Date: Tue, 9 Apr 2024 11:58:35 -0700 Subject: [PATCH] add paragraph about next work for multi-context libs --- blog/posts/whats-2024-brought-to-melange-so-far.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/blog/posts/whats-2024-brought-to-melange-so-far.md b/blog/posts/whats-2024-brought-to-melange-so-far.md index 7bc00af1b..687438492 100644 --- a/blog/posts/whats-2024-brought-to-melange-so-far.md +++ b/blog/posts/whats-2024-brought-to-melange-so-far.md @@ -254,9 +254,10 @@ This past quarter, we took it a step further. We added support in Dune for libraries that share the same name, as long as they're defined in different build contexts ([dune#10222](https://github.com/ocaml/dune/issues/10222)). Support for libraries with the same name in multiple contexts landed in -[dune#10307](https://github.com/ocaml/dune/pull/10307) and we'll be diving -deeper into what led us to this solution and what it enables in a separate blog -post. +[dune#10307](https://github.com/ocaml/dune/pull/10307). We'll be diving deeper +into what led us to this solution and what it enables in a separate blog post. +For now, the remaining work relates to selecting which build context to use for +editor integration when using multi-context builds. ## Community at large