Repository navigation
solveng:0.1.0 - #6175
Open
BierDav wants to merge 1 commit into
Open
solveng:0.1.0#6175BierDav wants to merge 1 commit into
BierDav wants to merge 1 commit into
Conversation
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am submitting
Description: solveng calculates the math you write, with units and every step shown. Inside a
solve-block, equations in the text ($I = 30 "mA"$,$t = Q_0 / I$) define values and are solved for their unknowns, and```solvengcode blocks are calculated line by line. Every result is shown with the rearranged formula, the substituted numbers and a sensible unit. It handles SI units with prefixes and custom units, inequalities, polynomials, systems, functions and plots, and tells units apart from variables (A,V,h, …) by how they are written. It's meant for engineering and physics homework, lab reports and calculation documents, where today the numbers are usually computed elsewhere and copied in by hand.I have read and followed the submission guidelines and, in particular, I
typst.tomlfile with all required keysREADME.mdwith documentation for my packageLICENSEfile or linked one in myREADME.mdexcluded PDFs or README images, if any, but not the LICENSETested with Typst 0.14.0 (the
compilerminimum) and 0.15.1: every README example compiles from this directory as@preview/solveng:0.1.0, andtypst-package-checkreports no issues. The tests, a fuzzer and the full reference live in the repository (tagv0.1.0).