Continuing the discussion from Feedback / Help Wanted: Upcoming OCaml.org Cookbook Feature: OK, let’s talk about an example that I came across recently: minttea/leaves/table.ml at b084ec7401c52167fae5087577133e52e3874899 · leostera/minttea · GitHub Here we want to render a table in the CLI and we want to pad and truncate the table content text to fit inside the column lengths. Eg suppose one of the columns is 30 characters long. So we need to calculate the length of the text that will go ...| OCaml
こんにちは! 食べログカンパニー開発本部ウェブ開発 2 部の濱口 (@machida4) です。 4 月 16 日 ~ 18 日に松山で開催された RubyKaigi 2025 に参加しました。 この記事では、RubyKaigi 2025 の注目セッションをご紹介します。 どのセッションも大変興味深いものばかりでしたが、全部盛りにするとスクロールバーが見えなくなってしまうので、特に印象に残ったセッションをいくつ...| Tabelog Tech Blog
Raku highlighting| docs.raku.org
The split() method of String values takes a pattern and divides this string into an ordered list of substrings by searching for the pattern, puts these substrings into an array, and returns the array.| MDN Web Docs
Unicode® Standard Annex #29| www.unicode.org
Unicode® Standard Annex #29| unicode.org
Unicode® Standard Annex #29| www.unicode.org
Don’t store string indices or offsets if possible. They aren’t stable over time or across runtime environments.| Ole Begemann
I’ve recently published my parsing combinator library lexy. One of the things it does is issue a lexy::error if the input does not match the grammar. This error has a .position() which gives you the position where the error occurred. In order to keep the happy path fast, .position() is not something that is easy to use for end users: it is simply an iterator into the input range. This is no good to a human user who wants something like line and column number to easily locate the problematic...| www.foonathan.net