Skip to content

Higher-order generic functions disobey kind system #1037

New issue
New issue
Closed
Closed
Higher-order generic functions disobey kind system#1037
Labels
A-type-systemArea: Type system

Description

@brson
brson
opened on Oct 13, 2011
fn spawn2<@T>(x: T, f: fn(T))  {
    f(x);
}

fn main() {
    fn foo<~T>(x: T) {
        log_err x;
    }

    spawn2::<@int>(@10, foo);
}

spawn2 is passing a shared kind to a function that only takes unique kinds.

Activity

  1. brson commented on Oct 13, 2011

    @brson
    brson
    on Oct 13, 2011
    ContributorAuthor

    There are probably similar issues with other generic types.

  2. ghost assigned
    marijnh
    on Nov 15, 2011

  3. marijnh commented on Nov 18, 2011

    @marijnh
    marijnh
    on Nov 18, 2011
    Contributor

    The restriction on taking the value of generics is currently making this impossible to reproduce.

    But even ignoring that, and updating the example to the new terminology, the current kind checker would catch that foo is being instantiated with a type that it doesn't accept. Closing (by #1177)

  4. marijnh
    closed this as completedon Nov 18, 2011
  5. brson
    unassigned
    marijnh
    on Jun 16, 2014
  6. coastalwhite
    added a commit that references this issue on Aug 5, 2023

    Convert shuffle_ps and shuffle_pd to const generics (rust-lang#1037)

    b0425e6
  7. U007D
    added 2 commits that reference this issue on Aug 21, 2026

    Merge rust-lang#1037

    d88a96b

    Auto merge of rust-lang#1037 - JOE1994:master, r=RalfJung

    0740a20
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

    A-type-systemArea: Type system

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions