sess should be a pure R package

已關閉
#1,829 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@renkun-ken 已經在處理了。

開始於 2026年10月5日。

  • #1830 來自 @renkun-ken —— 未關閉

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
重構
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
c, r, typescript
領域
desktop, devtools

研究方向

The issue identifies native C code in the sess package as the reason source installation needs a compiler, and points to the experimental Interactive runtime in issue #1805. Read that issue and compare the two proposed directions: split the bridge into a separate package, or remove it and simplify the backend. Done means ordinary sess installation no longer requires a compiler, with a chosen approach preserving the intended Interactive support.

由索引模型根據 Issue 內容生成。

描述

I think this should block 3.1.0.

sess now contains native C code for the experimental Interactive runtime (#1805).
As a result, installing the bundled package from source requires a compiler.

This is particularly problematic on Windows, where users may need to install the very large Rtools toolchain just to use ordinary vscode-R session integration, even though the native Interactive console bridge is not supported on Windows.

I see two possible directions:

  • Split the native Interactive bridge into a separate package, keeping the normal sess package compiler-free.
  • Remove the C bridge entirely and simplify the Interactive backend. Full Interactive functionality could initially be limited to the arf backend if necessary.

@renkun-ken Since R Interactive is still experimental, would you be open to prioritizing compiler-free installation and simplicity for 3.1.0, even if that means some Interactive features are initially available only with arf?

I don't think requiring Rtools as part of the normal vscode-R setup is acceptable.

主要語言
TypeScript
星號
1.2k
分支
151
平均合併
18 小時 16 分鐘
30 天內合併 PR
70

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

REditorSupport/vscode-R 的其他 Issue

查看 REditorSupport/vscode-R 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。