JuliaLang/julia

Do something else when method name is a TypeVar

Open

#33,537 建立於 2019年10月11日

在 GitHub 查看
 (7 留言) (3 反應) (0 負責人)Julia (48,709 star) (5,773 fork)batch import
buggood first issue

描述

I encountered the following behavior, which is just odd:

julia> T(a, b, c) where T = 1
T (generic function with 0 methods)

Apparently what happened was:

  1. It created a method T
  2. It added the defined method to something else (TypeVar, Any - one of them anyway)
  3. It returned the method T

According to @JeffBezanson this should do "something else, whatever it may be", so here's the issue for that.

貢獻者指南

技術棧
無
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Familiarity with Julia's type systemUnderstanding of method definition internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
The issue describes that defining a method with a TypeVar as the function name results in odd behavior (e.g., T(a,b,c) where T = 1). According to a comment from @JeffBezanson, this should do something else. To resolve this, one needs to investigate how method definitions are parsed and compiled in Julia, specifically in the parser and the module that handles method addition. Look at the source files related to method definition, such as method.c or builtins.c, and understand the intended behavior for a TypeVar as a method name. The goal is to decide what the correct behavior should be and implement it.
Do something else when method name is a TypeVar · JuliaLang/julia#33537 | Good First Issue