looks like image is broken.. ?

Description should be language-agnostic (function naming part)

No sample tests in crystal

python new test framework is required. updated in this fork

python new test framework is required. updated in this fork

Python: Random tests are vulnerable to input modification

python new test framework is required. updated in this fork

python new test framework is required. updated in this fork

Minor issue, but once in the "Task" section and twice in the "What each parameter looks like:" section the parameter 'fmt' is referred to as 'frm'.

Rules related to rounding are ambiguous, differ between languages, and have no spec how to break ties (i.e. perfect halves). In some languages behavior depends on the implicit, default rounding mode. Crystal tests were tricky to update because Crystal 0.24 used half-up, and Crystal 1.0 used half-to-even, and expected values of tests had to be adjusted to comform to the implicit default which changed from version to version.

There are some TypeScript test cases which are incorrect. The description very explicitly states that integer output should have a decimal point with a zero afterwards, and that all other numbers should be rounded to 3 decimal places. In some test cases, however, numbers are rounded to only 2 decimal places. It seems to be the case that when the final digit is a zero, it is omitted in the test cases. This appears to be the same issue that other users have been facing in other languages.

Examples:
expected 'h(t) = -16.0t^2 + 17.880t + 51.0' to equal 'h(t) = -16.0t^2 + 17.88t + 51.0'
expected 'x(t) = 33.340t' to equal 'x(t) = 33.34t'

hi in the first test case i have to insert 4 after the element 4 in the list and in the third test case i have to insert 2 before the element 2 in the list.

it is confusing

solution setup in Crystal does not build.