Direct execution of .trb

[pvcresin]

I find the T-Ruby syntax appealing because types are incorporated into the grammar.

On the other hand, by writing RBS comments in .rb files,

• type checking (by Sorbet, Steep or TypeProf)
• RBS file generation (by rbs-inline)
• direct execution

can all be achieved.

# a.rb
class A
  #: (Integer) -> String
  def foo(x)
    x.to_s
  end
end

While projects like ruby-next exist, transpilation is not yet as common in the Ruby community compared to the JavaScript community, so I thought T-Ruby might not be widely used.

Therefore, I thought that if T-Ruby could be directly executed, it could be said to have equivalent functionality to raw Ruby files with RBS comments written in them.

[yhk1038]

I'm sorry. I didn't get exactly what you are requesting.
Are you perhaps wanting a REPL console in the t-ruby version, similar to how ts-node is supported, like irb? (wow that's greate idea)

—

I also think rbs-inline is a greate attempt.

In fact, I tried to use rbs-inline myself.
However, I almost gave up on typing because of the inconvenience of "having to write comments and code separately while keeping them consistent."

That's why I thought of inline typing.

[pvcresin]

@yhk1038 I apologize for the confusion. Upon further reflection, this was more of a casual chat than a feature request.

My thought was, wouldn't it be nice if in the Ruby world, we could develop with just .trb files without generating .rb files, similar to how .ts files can be directly executed in the Node.js world?

To achieve this, as you mentioned, a tool that can directly specify and run .trb files, like ts-node, might serve as a starting point.

[yhk1038]

@pvcresin I'm still not fully understanding. I'd like to clarify by asking:
You mentioned above that "'direct execution' is implemented in the Node.js ecosystem" - could you tell me what specifically has been implemented in Node.js that you're referring to?

Thank you!

[pvcresin]

@yhk1038 I meant that in Node.js, you can directly execute .ts files with $ node main.ts.
Of course, I understand that it is internally converted to JavaScript and then executed.
However, I find it very appealing that it can be controlled with simple flags alone.
(e.g., --experimental-strip-types and --experimental-transform-types)

Personally, I would like to be able to execute it similarly, like $ ruby main.trb, and I was calling this 'direct execution'.

However, I believe that getting it incorporated into the main Ruby project would be a high hurdle, so the reason for opening this issue is that it would be nice to have a tool that provides a direct execution experience for Ruby, similar to ts-node.

Therefore, I thought it would be good if, for example, $ t-ruby main.trb could directly execute it without generating .rb or .rbs files.

I'm sorry for the unclear writing.

[yhk1038]

@pvcresin Finally, absolutely i got it. Sorry for my misunderstand. It is so reasonable idea!

[yhk1038]

@pvcresin Since the trc command stands for the t-ruby "compiler,"
direct execution was created by appending the run sub-command.

At the same time, since t-ruby files are executed, I thought it would be reasonable to add an interface that executes files with the corresponding extension by name, similar to ruby or python. Therefore, I'm adding the new t-ruby command as suggested.

trc run <.trb file> internally executes t-ruby <.trb file>, with options delegated.

Plz check #37 for more detail.

This improvement is within the v0.0.5 milestone, which is scheduled to be completed by mid-January, so it will be patched in the preceding v0.0.4x releases.

[pvcresin]

@yhk1038 I'm impressed by your quick work! I completely agree with your implementation approach.