eZio Pan
eZio Pan
@ZhangHanDong @angelrain1 我想两位说的应该是近似的意思了。本质上我们都是对同一个内容的不同描述方法，都没错。我的描述中将加法解释为并集比较符合数学上的直觉，而将**冒号**解释为**限制**是来源于冒号在 Rust 通常用法下的衍生：对变量的类型的限制。 这里我也建议张老师在这段体现一下 `实类型` 和 `泛型标记` 之间的差别，直接使用 `T` 和 `T:Trait(s)` 可能太容易让人混淆了。就像在描述函数的声明和调用的时候要区分 `形式参数`（`parameter`） 和 `实际参数`（`argument`） 一样，区分出来就更明确了。
Yes, I think Node.py causes it. But for most situation, Node.py just does right. Since most python source code will be place in directory that user has privilege to write....
i find a dirty way to get the path ``` {{ $raw_info := printf "%v" (os.Stat .File) }} {{ $filename_string := index (findRE "filename:.* fs:" $raw_info) 0 }} {{ $filename_string...
in Fedora 37, if there is no `xrandr` installed, `exitcode` is `255`.
@burrbull thanks for point it out! @newAM would you consider remove `stm32f4` tag? Or add `g4` `wb` `h7` `f7` `l4`?
> I left comments in Issue #2409 with my understanding what happened. > It's still unclear to me, whether this approach fits the new timer hierarchy. Ah, I'm terribly sorry...
> I can squash the commits, if you agree to the current state. Yeah! It looks good to me! And I also test PWM output on my dev board with...
edit from @jamesmunns: added to the list above
| Chip | Type | memory.x | DS Tab.2 | Note | | :---------: | :--: | :------: | :-------: | :--: | | STM32F411RE | RAM | 64K |...
| Chip | Type | memory.x | DS Tab.2 | Note | | :-----------------: | :----: | :------: | :--------------------: | :----------------: | | STM32H5[67]xx[IG] | RAM | 256 K...