Jeremy L Thompson

Since @YohannDudouit made a pretty comprehensive review on the overall structure and I agree with many of his points, I focused on creating a few issues highlighting some more Rust...

> * All of the internal calls to .unwrap() are made when I **know** that a function call will not return an Err. For example, in the [`global_h_refinement()`](https://docs.rs/fem_2d/latest/fem_2d/domain/mesh/struct.Mesh.html#method.global_h_refinement) method on...

My issues have been addressed. One minor point - I suspect 'galerking sampling' on page 6, footnote 1 should be 'Galerkin Sampling'

This exact code is passing for me. It may be [another] Apple following web standards issue?

I strongly disagree. We should be teaching programming that helps people get job critical skills, not teaching people to write hacky code that happens to pass challenges. In the specific...

I would assume it is a change somewhere here: https://github.com/freeCodeCamp/freeCodeCamp/commits/main/curriculum/test/test-challenges.js But this stuff is hieroglyphs to me and I don't see anything that would obviously cause the change.

That seems like a reasonable thing to do for the regex tests, but it lets a ton of bad code through for the rest of the JavaScript challenges.

This also makes the Project Euler solutions run slower by wiping any cached values, which makes it harder to show the benefits of memoization for people doing the interview prep...

Hmm, if it isn't possible to selectively reset the global space only for some challenges, that might be the way to go.

I think saying that the keyword `function` is replaced with the keyword `constructor` is literally true but also not very useful of an observation.