Description of Change

Checklist

• Added description of change
• Added file name matches [File

Description of Change

References

Checklist

We could improve the Error: output to a user shown in the expression preview to tell them what the Type() is for a parameter being passed that is not compatible with the parameter type being expected.

Proposed solution

On our various HTML/XML GREL functions (htmlText(), wholeText(), ownText(), etc.) add the new Type().call(bindings, args) to the EvalError and rephrase the error text as n

steps to reproduce

Write a loop, from 1 to 80000, each time add a random int to the max heap.

In theory it takes very little time(NlogN, N=80000, <1sec ), but the program does take a long time.

I'v also tested the BinaryHeap in https://github.com/SolutionsDesign/Algorithmia, it performs well, so it is probably due to the bad algorithm.

In the following file we have already ported some tests from Go to Rust:
https://github.com/crossbeam-rs/crossbeam-channel/blob/master/tests/golang.rs

The idea is to blindly port all the tests for Go channels line by line, which will give us additional confidence in the correctness of crossbeam-channel.

In the test file, you can find stubs with links to the original tests written in Go and