tamago324 tamago324

name	explain-diff-html
description	Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

Explain Diff

Please make me a rich, interactive explanation of the specified code change.

It should have these sections:

結城浩とChatGPTの対話

2022年12月2日

「質問」は結城浩の文章です。
「回答」はChatGPTの文章です。

質問

ChatGPTという対話するAIツールがあります。人間が質問を投げかけるとそれらしく対話して回答してくれるツールです。こういうツールに対してどんな質問を投げかけたらおもしろい対話になるでしょうかね。何かアイディアがあったら聞かせてください。具体的な質問を知りたいなあ。

並置による関数適用

並置による関数適用の善し悪しについて盛り上っているので、自分の意見を表明しておく。以下の2本立て。

純粋に構文論的な議論 (構文拡張の余地を残す)
意味論との関係での議論 (副作用の表示)

先に結論だけ書くと、私はどちらかといえば括弧による関数適用のほうが好みです。

そもそも並置による関数適用とは

GameBall を US から買う

すごいって噂のトラックボール。

界隈では去年くらいから噂だったらしい。自分は vim-jp 経由で最近知った。

Redirects in React Router v6

An important part of "routing" is handling redirects. Redirects usually happen when you want to preserve an old link and send all the traffic bound for that destination to some new URL so you don't end up with broken links.

The way we recommend handling redirects has changed in React Router v6. This document explains why.

Background

In React Router v4/5 (they have the same API, you can read about why we had to bump the major version here) we had a <Redirect> component that you could use to tell the router when to automatically redirect to another URL. You might have used it like this:

A half-hour to learn Zig

This is inspired by https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/

Basics

the command zig run my_code.zig will compile and immediately run your Zig program. Each of these cells contains a zig program that you can try to run (some of them contain compile-time errors that you can comment out to play with)

	FROM denoland/deno:latest

	# Create the application directory
	WORKDIR /app

	# Copy dependency files first for caching
	COPY deno.json deno.lock* ./

	# Copy the rest of the application code
	COPY . .

	html {
	--crust: #dce0e8;
	--mantle: #e6e9ef;
	--base: #eff1f5;
	--surface0: #ccd0da;
	--surface1: #bcc0cc;
	--surface2: #acb0be;
	--overlay0: #9ca0b0;
	--overlay1: #8c8fa1;
	--overlay2: #7c7f93;

	{
	"als": "https://raw.githubusercontent.com/AdaCore/ada_language_server/master/integration/vscode/ada/package.json",
	"astro": "https://raw.githubusercontent.com/withastro/language-tools/main/packages/vscode/package.json",
	"awkls": "https://raw.githubusercontent.com/Beaglefoot/awk-language-server/master/client/package.json",
	"bashls": "https://raw.githubusercontent.com/bash-lsp/bash-language-server/master/vscode-client/package.json",
	"clangd": "https://raw.githubusercontent.com/clangd/vscode-clangd/master/package.json",
	"cssls": "https://raw.githubusercontent.com/microsoft/vscode/main/extensions/css-language-features/package.json",
	"dartls": "https://raw.githubusercontent.com/Dart-Code/Dart-Code/master/package.json",
	"denols": "https://raw.githubusercontent.com/denoland/vscode_deno/main/package.json",
	"elixirls": "https://raw.githubusercontent.com/elixir-lsp/vscode-elixir-ls/master/package.json",

	-- put this file somewhere in your nvim config, like: ~/.config/nvim/lua/config/lua-lsp.lua
	-- usage: require'lspconfig'.sumneko_lua.setup(require("config.lua-lsp"))

	local library = {}

	local path = vim.split(package.path, ";")

	-- this is the ONLY correct way to setup your path
	table.insert(path, "lua/?.lua")
	table.insert(path, "lua/?/init.lua")