puzzler | 一个高效快速的前端页面切图工具，用于将一张图片快速切割成切片并导出 HTML | Canvas library

This has nothing to do with IIFE, this is just var hoisting as you guessed. You would have the same situation with a classic function.

The fact that you redeclared name somewhere in the IIFE cancels the global scope of name within this IIFE. So the first time you call name within your IIFE, it behaves as undeclared and is thus undefined.

You can test the var hoisting concept with this little fiddle by commenting and uncommenting a line.

Here's a regex-based approach to the problem. We form a regex from lookup_word by adding .* between each letter in the word. Then we attempt to match the regex against word. Since .* is inherently greedy, you will get the longest possible match inside word. You can then compare the length of the matched string to the length of lookup_word, and if the matched string is longer, then lookup_word is a kangaroo word:

You use "while True:" when you want something to happen forever.I think you should just take it out from ask_for_words.

This is due to Constant Promotion:

Promotion of a value expression to a 'static slot occurs when the expression could be written in a constant, borrowed, and dereferencing that borrow where the expression was originally written, without changing the runtime behavior. That is, the promoted expression can be evaluated at compile-time and the resulting value does not contain interior mutability or destructors (these properties are determined based on the value where possible, e.g. &None always has the type &'static Option<_>, as it contains nothing disallowed).

Update: There's community project called SerilogAnalyzer that can generate the contents of appSettings.json and app.config from a C# Serilog pipeline. It's super cool!

There's nothing built-in into Serilog that allows you to do that, and you wouldn't be able to simply serialize the LogConfiguration to text the way you're thinking about it, because most of the configuration is not stored in simple variables, but instead in lambda functions that are created during the creation of the pipeline.

Either way, you'd have to resort to using Reflection to inspect any of the configured sinks and their properties. You can see a related example on this answer:

Unit test Serilog configuration

That said, I personally think using the fluent API is the way to go, instead of using the JSON config (or the XML app.config) because sooner or later you'll want to make some sinks asynchronous, and/or use a predicate or a function to configure certain aspects of the pipeline (for example, to configure a sub-logger), and it will very hard (and in some cases impossible) to configure in the JSON/XML config anyway.

You can use the options pattern to configure the small parts that you think you might want to change via configuration (such as URLs, logging levels, etc), and the rest of it, use the fluent API combined with conditional sinks.

Because this `campus_dataJSON`->'$.u_email' = 'dr@kol.vop' throws an error:

After trial and error, I discovered the problem was with the Hexagon.scale property. By removing it from serialization the rest of the Deserialize began to work properly.

It is a recursive method call. There is a limitation for stack call so when numbers of call reach the limitation in try block it throws a stack overflow exception. After the exception, it tries to run the code in the final block. But due to the limitation, it raises another exception that causes to exit form the nested method call and makes a free space for another method call. This scenario is repeated in the outer level again and again. Once it gets a free space in the stack it attempts to fill it by another method call. This is why it continues up to there is no memory.

Any solution here will be very difficult to compact into a single statement, and avoiding some sort of looping structure will also be very difficult. Here's a solution that involves a cursor.

By the way, using an approach like this, table3 is redundant. At least, I didn't end up needing it.