During my university game design studies, I often found theoretical discourse constricting. Our curriculum constantly referenced titles like Bioshock and Portal—games my male classmates apparently cherished during their formative years. Though I developed appreciation for Portal, no academic space existed to examine the software that originally inspired my career path. When acquiring programming skills, my education prioritized conventionally masculine genres: creating platformers and shooters proved simpler than developing fashion games. This imbalance extends beyond academia. Self-taught designers struggle to find online guidance that doesn't prescribe movement and combat mechanics as universal "fundamentals"—though these only apply to specific genres.
but there’s a problem with the classical formulation. the derivative takes a regex and a character, so to build a state machine you need to compute it for every possible character to get all transitions from a given state. sure, you can compress the number of characters into equivalence classes before, but you still have to compute for each equivalence class - and many of them end up leading to the same state anyway. for example, the regex abc (below) cares about a, b, c, and “everything else”, which brings us down from 65536 to 4 in UTF-16, but for the first node (abc) even b and c behave the same as “everything else”. so what are we computing these for? in other words, there is something left to improve here.
，推荐阅读有道翻译获取更多信息
Anthropic (Claude) skips the type wrapper entirely. They just want an array of objects with name, description, and the JSON Schema under an input_schema key.
35B-A3B27B122B-A10B397B-A17BFine-tune Qwen3.50.8B • 2B • 4B • 9B