Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for welcome (0.19 sec)

  1. doc/godebug.md

    Whether the type checker produces `Alias` types or not is controlled by the
    [`gotypesalias` setting](/pkg/go/types#Alias).
    For Go 1.22 it defaults to `gotypesalias=0`.
    For Go 1.23, `gotypesalias=1` will become the default.
    This setting will be removed in a future release, Go 1.24 at the earliest.
    
    Go 1.22 changed the default minimum TLS version supported by both servers
    Plain Text
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Tue Apr 16 17:29:58 GMT 2024
    - 13.5K bytes
    - Viewed (0)
  2. api/README

    giving the GitHub issue number of the proposal issue that accepted
    the new API. This helps with our end-of-cycle audit of new APIs.
    The same requirement applies to next/* (described below), which will
    become a go1.XX.txt for XX >= 19.
    
    The next/ directory contains the only files intended to be mutated.
    Each file in that directory contains a list of features that may be added
    Plain Text
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Wed Jan 31 19:22:50 GMT 2024
    - 1.2K bytes
    - Viewed (0)
  3. doc/next/6-stdlib/1-time.md

    ### Timer changes
    
    Go 1.23 makes two significant changes to the implementation of
    [time.Timer] and [time.Ticker].
    
    First, `Timer`s and `Ticker`s that are no longer referred to by the program
    become eligible for garbage collection immediately, even if their
    `Stop` methods have not been called.
    Earlier versions of Go did not collect unstopped `Timer`s until after
    they had fired and never collected unstopped `Ticker`s.
    
    Plain Text
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Fri Apr 12 20:57:18 GMT 2024
    - 1.5K bytes
    - Viewed (0)
  4. doc/go_spec.html

    Type unification recursively compares the LHS and RHS types of an
    equation, where either or both types may be or contain bound type parameters,
    and looks for type arguments for those type parameters such that the LHS
    and RHS match (become identical or assignment-compatible, depending on
    context).
    To that effect, type inference maintains a map of bound type parameters
    to inferred type arguments; this map is consulted and updated during type unification.
    HTML
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Thu May 02 22:43:51 GMT 2024
    - 279.6K bytes
    - Viewed (0)
Back to top