Named contexts

Contexts may include a name property for distinguishing them from other contexts. This is particularly useful inside pick alternatives, where several possible contexts may apply at a given point in execution and runtime information is needed to select which one is active.

Explore
View source
Playground

Loading ....

YAML
JSON

ethdebug/format/program/context/name
$schema: "https://json-schema.org/draft/2020-12/schema"
$id: "schema:ethdebug/format/program/context/name"

title: ethdebug/format/program/context/name
description: |
  A label for distinguishing this context from other contexts.
  This is particularly useful inside `pick` alternatives,
  where several possible contexts may apply at a given point in
  execution and runtime information is needed to select which one
  is active.

  Context names are opaque strings with no format-imposed semantics.
  Compilers **should** choose names that are meaningful to debugger
  users.

type: object
properties:
  name:
    type: string
required:
  - name

examples:
  # example: naming an inlined call site
  - name: "inlined-call"
  # example: naming a generic instantiation
  - name: "Array<T=bytes32>"

ethdebug/format/program/context/name
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "schema:ethdebug/format/program/context/name",
  "title": "ethdebug/format/program/context/name",
  "description": "A label for distinguishing this context from other contexts.\nThis is particularly useful inside `pick` alternatives,\nwhere several possible contexts may apply at a given point in\nexecution and runtime information is needed to select which one\nis active.\n\nContext names are opaque strings with no format-imposed semantics.\nCompilers **should** choose names that are meaningful to debugger\nusers.\n",
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    }
  },
  "required": [
    "name"
  ],
  "examples": [
    {
      "name": "inlined-call"
    },
    {
      "name": "Array<T=bytes32>"
    }
  ]
}