Syside 0.10.3 is a patch release, so most of it is bug fixes and performance work — but if you regularly work with large models or lean on Syside to catch modeling mistakes, it’s worth updating.
The headline for anyone working at scale is performance. Grid views load noticeably faster, and textual parsing has been sped up for the case where large models are edited rapidly by agents or scripts — so automated workflows spend less time waiting and no longer introduce “phantom errors”.
Our in-house Modeler CLI diagram generation keeps improving, and this release focuses on how inherited features are drawn. The difference is easiest to just show — here’s the same model and view rendered before (on the left) and after (on the right):
Inherited features now are collected correctly and rendered with a dashed line, showing clearly what’s in your elements.
Another reason to update is stronger type checking. Syside now validates connections in real time and flags when the things you’re wiring together don’t actually match. In the example below, it catches that my_headphones (a 3.5mm jack) can’t be plugged into my_amplifier (a 6.3mm port) — exactly the kind of mismatch that’s easy to miss now and annoying to debug later, especially if you rely on your SysMLv2 models for auto-generation of code or ICDs.
Calculation definitions can now be recursive, too. It’s a small change, but it makes expressible some things that simply weren’t before — like computing the n-th Fibonacci number directly in SysMLv2.
Beyond that, this release smooths some day-to-day friction. You can open grid views straight from the textual model with a right-click, grid views now show a loading bar as they load, anonymous elements in matrix views say so explicitly, and clickable errors in the SysMLv2 Views Pane jump you straight to whatever is blocking a view from rendering. The syside check command now confirms with “All checks passed”, and its --stats flag lists every user file it checked so you can be sure nothing slipped through. The formatter can skip the automatic package-closing comment (// package MyPackage) if you’d rather it didn’t, and you’ll get a clearer error when a reserved keyword like fork is used as a name.