Column reference as a string.
Arguments:
Name | Description | Example |
---|
I'm sure there must be a reason (valid or historical) but distinguishing between input and output types seems to serve no real purpose and comes with a significant cost.
By no means the authority but perhaps a good starting point are the reasons that ChatGPT give:
In GraphQL, the distinction between regular types (also known as output types) and input types serves a specific purpose to ensure clarity, maintainability, and type safety. While it might seem convenient to use any type as an input type, there are valid reasons for this separation:
Please ChatGPT, do tell...
#!/usr/bin/env bash | |
set -euo pipefail | |
# Ever move a file, merge main, then get hit with this? | |
# | |
# Deleted merge conflict for 'foo.txt': | |
# {local}: deleted | |
# {remote}: modified file | |
# Use (m)odified or (d)eleted file, or (a)bort? | |
# |
// TODO: Determine whether we need traceKitWindowOnError to map the errors too.
dom.window.asInstanceOf[std.Window].onerror = toUnionLeft(onErrorEventHandler _)
private def onErrorEventHandler(
event: dom.Event | String,
source: js.UndefOr[String],
lineno: js.UndefOr[Double],
scalacOptions ++= Seq(
"-Ybrowse:typer",
"-Xprint:typer",
"-Xlog-implicits"
)
package errors | |
import scala.concurrent.{ExecutionContext, Future} | |
import scala.language.{implicitConversions, reflectiveCalls} | |
import scala.scalajs.js | |
object Errors { | |
def mapJsError( | |
message: String, |
These are some of the weird cases I encountered for suzaku-io/boopickle#21.
Full repo is here https://github.com/steinybot/bug-reports/tree/boopickle/diverging-implicits.
Something smells fishy...
#!/usr/bin/env bash | |
set -euo pipefail | |
REPEATS=100 | |
OUTPUT_FILE='results.csv' | |
run_tests() { | |
echo "Benchmarking ${COMMAND[@]}" |