Skip to content

docs: token is not defined, but mentioned #116666

Closed

Description

@Privat33r-dev

The token term is not being explained (even by means of reference), but mentioned in the chapters 8 and 14 of the tutorial, maybe it can be a good point to add a reference as well?

As a potential solution, we can add another entry in the glossary to shortly provide a basic intuition for a token/code unit. In general, introduction of the term might be of use to explain some concepts, such as error highlighting/handling, syntax. Maybe it would even make sense to introduce it right in the chapter 8 along with error handling.

I would like to see other perspectives on this question.

Originally posted by @Privat33r-dev in #116569 (comment)

Linked PRs

Activity

  1. Almas-Ali commented on Mar 13, 2024

    @Almas-Ali

    I think this needs to be updated. We should add some definition to token. It will be hard to get the proper meaning of this term. We can add 1/2 line to describe what the token term means here. 

  2. AkashKumarSingh11032001 commented on Mar 14, 2024

    @AkashKumarSingh11032001

    Hi @Privat33r-dev, i think you are right, after going through the following docs, it clear that the word "token" is required to be defined (in case of any beginner try to understand, it would be difficult for them to understand).

  3. added a commit that references this issue on Mar 5, 2025
  4. added a commit that references this issue on Mar 17, 2025
  5. added 2 commits that reference this issue on Mar 17, 2025
  6. added a commit that references this issue on Mar 17, 2025
  7. added 2 commits that reference this issue on Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc dir

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions