algorithmic:0.1.0

[lf-]

I am submitting

• a new package
• an update for a package

I have read and followed the submission guidelines and, in particular, I

• selected a name in conformance with the guidelines

  My read of the guidelines is that "algorithm" here would be wrong, but "algorithmic" seems sufficiently funky to not be purely descriptive.

• added a typst.toml file with all required keys

• added a README.md with documentation for my package

• have chosen a license and added a LICENSE file or linked one in my README.md

  I am REUSE compliant and all the files have license headers. The actual license is in LICENSES/MIT.txt

• ensured that my submission does not infringe upon the rights of a third party

• tested my package locally on my system and it worked

• named this PR as name:version of the submitted package

• agree that my package will not be removed without good reason

Description: This package provides facilities for typesetting algorithmic pseudocode, inspired by algorithmicx for LaTeX.

Screenshot:

[laurmaedje]

One more thing: The package directory layout just changed. It's now packages/preview/package/version instead of packages/preview/package-version.

[lf-]

git mistake 😆

should be in the new structure now.

[likern]

I've tested a bit this package.

Some functions return content, for example FnI("Func", "a") call, while others return array, like Cmt:

#let Cmt(c) = (Ic(c),)

And these functions are not composable.
If I try to call Cmt inside content I get this output (definitely not desired):

#algorithm({
  import algorithmic: *

  Cmt[Comment: #Cmt[Nested Comment]]
})

But if I try to call FnI at top-level (or in other places where array is expected and joined together - in any code block)
I get criptic message "Cannot join content with array"

which is quite annoying.

I think this limits package usability (while I much like it). For example I can't create my own custom functions like using if in assignment.

Is there possible fix or workaround exists?

[lf-]

This is completely intentional and unavoidable. See the readme regarding "inline".

[laurmaedje]

Thank you!