Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REFACTOR] Polish runtime #4729

Merged
merged 1 commit into from
Jan 17, 2020
Merged

[REFACTOR] Polish runtime #4729

merged 1 commit into from
Jan 17, 2020

Conversation

tqchen
Copy link
Member

@tqchen tqchen commented Jan 16, 2020

  • Remove operator bool from base object ref macro
    • Raitionale: operator bool can be dangerous for sub-classes
      that also overloads other operators(e.g. ==).
    • If bool is still needed, use explicit operator bool.
  • Use absolute include when necessary
  • Move type related util to data_type
  • Isolate stackvm code from compiler

cc @icemelon9 @ZihengJiang

@tqchen tqchen force-pushed the object branch 3 times, most recently from 64c2483 to a5107f9 Compare January 16, 2020 22:58
- Remove operator bool from base object ref macro
  - Raitionale: operator bool can be dangerous for sub-classes
    that also overloads other operators(e.g. ==).
  - If bool is still needed, use explicit operator bool.
- Use absolute include when necessary
- Move type related util to data_type
- Isolate stackvm code from compiler
@tqchen tqchen merged commit b171cf1 into apache:master Jan 17, 2020
alexwong pushed a commit to alexwong/tvm that referenced this pull request Feb 26, 2020
- Remove operator bool from base object ref macro
  - Raitionale: operator bool can be dangerous for sub-classes
    that also overloads other operators(e.g. ==).
  - If bool is still needed, use explicit operator bool.
- Use absolute include when necessary
- Move type related util to data_type
- Isolate stackvm code from compiler
alexwong pushed a commit to alexwong/tvm that referenced this pull request Feb 28, 2020
- Remove operator bool from base object ref macro
  - Raitionale: operator bool can be dangerous for sub-classes
    that also overloads other operators(e.g. ==).
  - If bool is still needed, use explicit operator bool.
- Use absolute include when necessary
- Move type related util to data_type
- Isolate stackvm code from compiler
zhiics pushed a commit to neo-ai/tvm that referenced this pull request Mar 2, 2020
- Remove operator bool from base object ref macro
  - Raitionale: operator bool can be dangerous for sub-classes
    that also overloads other operators(e.g. ==).
  - If bool is still needed, use explicit operator bool.
- Use absolute include when necessary
- Move type related util to data_type
- Isolate stackvm code from compiler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants