最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

javascript - What does "syntax tax" mean in respect to the TC39 pipe-operator proposal? - Stack Overflow

matteradmin6PV0评论

Reading the ECMAScript TC39 pipe-operator proposal; it mentions "syntax tax" when comparing 2 possible alternatives for the pipe-operator implementation (see #hack-pipes-favor-more-common-expressions).

I interpret this to mean that for example extra syntax is required. E.g. for F#-pipes you need to wrap non-unary functions in a lambda taking a single argument to work. So the "tax" is the added extra syntax that is needed to make that work.

(Perhaps this is more a question of general use of English, and I'm not used to how "tax" is used in other contexts.)

Post a comment

comment list (0)

  1. No comments so far