Skip to content

Conversation

@starwarfan
Copy link
Contributor

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

  • N
  • Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

  • Affects user behaviors
  • Contains CI/CD configuration changes
  • Contains documentation changes
  • Contains experimental features
  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

  • N
  • Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

  • Unit test
  • Integration test
  • Benchmark (add benchmark stats below)
  • Manual test (add detailed scripts or steps below)
  • Other

6. Release note

None

@starwarfan starwarfan marked this pull request as draft December 22, 2025 09:27
@starwarfan starwarfan marked this pull request as ready for review December 23, 2025 02:50
- [x] 9.1 Add OpenSpec project structure and configuration
- [x] 9.2 Create AGENTS.md with AI assistant instructions
- [x] 9.3 Set up spec-driven development workflow
- [x] 9.4 Configure change proposal management system
Copy link
Contributor

@zoowii zoowii Jan 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. after I reviewed this PR, you need to openspec.archive this change(after that, the change dir will be moved to openspec/changes/archives and update the openspec/specs
  2. When creating a PR, do not include openspec.archive. After the code review is basically completed, add openspec.archive as a separate commit to this PR.
  3. why there are some not marked todo items in tasks.md

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because I created this change using existing commit, so there are some not implemented items in tasks.md, shall I let openspec finish those unmarked items?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, use AI to create a TODO-SPECS.md under openspec directory, and mark the status of the features and sub tasks

- **Core Language**: C++ (primary implementation)
- **Runtime Support**: C, Rust APIs
- **Compilation**: CMake build system
- **JIT Backend**: LLVM 15 (for Lazy-JIT mode)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

llvm 15 is not jit backend, but we use some base data structures in it

@zoowii
Copy link
Contributor

zoowii commented Jan 5, 2026

lgtm, you can archive this change now

@zoowii zoowii merged commit 11f88d4 into DTVMStack:main Jan 5, 2026
9 checks passed
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