diff options
Diffstat (limited to 'docs/posts')
8 files changed, 45 insertions, 0 deletions
diff --git a/docs/posts/cpp-you-can-use-keywords-in-attributes/index.html b/docs/posts/cpp-you-can-use-keywords-in-attributes/index.html index 874ddcb..21411bc 100644 --- a/docs/posts/cpp-you-can-use-keywords-in-attributes/index.html +++ b/docs/posts/cpp-you-can-use-keywords-in-attributes/index.html @@ -156,6 +156,12 @@ $ clang++ –std=c++17 hoge.cpp</p> <p>「<code>identifier</code> の構文上の要件を満たさないような代替トークン」はこれらが当てはまると思われる。</p> <p>調べた感想: 字句解析器か構文解析器が辛そう</p> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/cpp">cpp</a></li> + <li><a href="https://blog.nsfisis.dev/tags/cpp17">cpp17</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/phperkaigi-2021/index.html b/docs/posts/phperkaigi-2021/index.html index 977be03..659b8df 100644 --- a/docs/posts/phperkaigi-2021/index.html +++ b/docs/posts/phperkaigi-2021/index.html @@ -568,6 +568,13 @@ Nginx などで相互に gRPC と gRPC-Web で変換</p> (ずっと常体で書いてしまったのでいきなり仏頂面から笑顔になったようで気持ち悪い)</p> <p>ではまた来年。</p> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/conference">conference</a></li> + <li><a href="https://blog.nsfisis.dev/tags/php">php</a></li> + <li><a href="https://blog.nsfisis.dev/tags/phperkaigi">phperkaigi</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/python-unbound-local-error/index.html b/docs/posts/python-unbound-local-error/index.html index 227164a..cba8819 100644 --- a/docs/posts/python-unbound-local-error/index.html +++ b/docs/posts/python-unbound-local-error/index.html @@ -128,6 +128,12 @@ f() g() </code></pre></div><p><code>(*)</code> のように、<code>nonlocal</code> を追加する。これにより一つ外側のスコープ (<code>g</code> の一つ外側 = <code>f</code>) で定義されている <code>x</code> を探しに行くようになる。</p> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/python">python</a></li> + <li><a href="https://blog.nsfisis.dev/tags/python3">python3</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/ruby-detect-running-implementation/index.html b/docs/posts/ruby-detect-running-implementation/index.html index f4642b5..09d79aa 100644 --- a/docs/posts/ruby-detect-running-implementation/index.html +++ b/docs/posts/ruby-detect-running-implementation/index.html @@ -158,6 +158,11 @@ jruby 1.2.0 (ruby 1.8.6 patchlevel 287) (2009-03-16 rev 9419) [i386-java] </span><span style="color:#75715e"> */</span> <span style="color:#75715e">#define MRUBY_RUBY_ENGINE "mruby" </span></code></pre></div></div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/ruby-then-keyword-and-case-in/index.html b/docs/posts/ruby-then-keyword-and-case-in/index.html index f055f34..08e90bd 100644 --- a/docs/posts/ruby-then-keyword-and-case-in/index.html +++ b/docs/posts/ruby-then-keyword-and-case-in/index.html @@ -224,6 +224,12 @@ C系の <code>if</code> 後に来る <code>(</code>/<code>)</code> や、Python <li>Ruby の構文を正確に知るには (現状) <code>parse.y</code> を直接読めばよい</li> </ul> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> + <li><a href="https://blog.nsfisis.dev/tags/ruby3">ruby3</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/rust-where-are-primitive-types-from/index.html b/docs/posts/rust-where-are-primitive-types-from/index.html index ab5e557..8253d6f 100644 --- a/docs/posts/rust-where-are-primitive-types-from/index.html +++ b/docs/posts/rust-where-are-primitive-types-from/index.html @@ -215,6 +215,11 @@ rustc_resolve/src/lib.rs: table.insert(sym::i128, Int(IntTy::I128)); <h1 id="まとめ">まとめ</h1> <p>Rust のプリミティブ型は予約語ではない。名前解決の最終段階で特別扱いされ、他に同名の型が見つかっていなければ対応するプリミティブ型に解決される。</p> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/rust">rust</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html b/docs/posts/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html index 082c7d1..ef5ec96 100644 --- a/docs/posts/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html +++ b/docs/posts/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html @@ -168,6 +168,11 @@ FileEncoding Obsolete. It still works and is equivalent </ul> <p>ところでこの調査で知ったのだが、<code>BufRead</code> と <code>BufWrite</code> は上にある通り発火するタイミングが「後」と「前」で対称性がない。可能なら <code>Pre</code>/<code>Post</code> 付きのものを使った方が分かりやすいだろう。</p> </div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> + </ul> + </footer> </article></main> <footer class="footer"> diff --git a/docs/posts/vim-swap-order-of-selected-lines/index.html b/docs/posts/vim-swap-order-of-selected-lines/index.html index b290e21..09a1e8a 100644 --- a/docs/posts/vim-swap-order-of-selected-lines/index.html +++ b/docs/posts/vim-swap-order-of-selected-lines/index.html @@ -181,6 +181,11 @@ executing autocommands |autocmd-searchpat|. </span><span style="color:#960050;background-color:#1e0010"></span> \ <span style="color:#a6e22e">Reverse</span><span style="color:#960050;background-color:#1e0010"> </span><span style="color:#960050;background-color:#1e0010"></span> \ <span style="color:#a6e22e">keeppatterns</span> <<span style="color:#a6e22e">line1</span>>,<<span style="color:#a6e22e">line2</span>><span style="color:#a6e22e">g</span><span style="color:#e6db74">/^/</span><span style="color:#a6e22e">m</span><<span style="color:#a6e22e">line1</span>><span style="color:#ae81ff">-1</span><span style="color:#960050;background-color:#1e0010"> </span></code></pre></div></div> + <footer class="post-footer"> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> + </ul> + </footer> </article></main> <footer class="footer"> |