# Is it still planned for main to get a second argument or is this an outdated idea?

**URL:** <https://ziggit.dev/t/is-it-still-planned-for-main-to-get-a-second-argument-or-is-this-an-outdated-idea/18192>\
**Category:** Help\
**Tags:** standard-library\
**Created:** [November 2, 2026, 10:52pm UTC](https://ziggit.dev/t/is-it-still-planned-for-main-to-get-a-second-argument-or-is-this-an-outdated-idea/18192 "2026-11-02T22:52:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![THE\_DRINK](https://ziggit.dev/user_avatar/ziggit.dev/the_drink/32/10506_2.png) [@THE\_DRINK](https://ziggit.dev/u/THE_DRINK)\
**Post date:** [November 2, 2026, 10:52pm UTC](https://ziggit.dev/t/is-it-still-planned-for-main-to-get-a-second-argument-or-is-this-an-outdated-idea/18192/1 "2026-11-02T22:52:28Z")

</div>

while i was reading some docs a came across  
[https://codeberg.org/ziglang/zig/src/commit/aca58dd61a80f8bfe162ee9f715a605b4066f9c0/lib/std/process.zig#L28-L30](https://codeberg.org/ziglang/zig/src/commit/aca58dd61a80f8bfe162ee9f715a605b4066f9c0/lib/std/process.zig#L28-L30)

which implies that main would take a second argument is there any plans for that or is this comment outdated maybe ?

---

<div class="post-metadata">

**Author:** ![ScottRedig](https://ziggit.dev/user_avatar/ziggit.dev/scottredig/32/5880_2.png) [@ScottRedig](https://ziggit.dev/u/ScottRedig)\
**Post date:** [November 2, 2026, 11:17pm UTC](https://ziggit.dev/t/is-it-still-planned-for-main-to-get-a-second-argument-or-is-this-an-outdated-idea/18192/2 "2026-11-02T23:17:55Z")

</div>

Kinda, see [https://codeberg.org/ziglang/zig/issues/30677](https://codeberg.org/ziglang/zig/issues/30677)

It will be a method on init, rather than a second argument.

The issue linked in the code comment is closed with a [codeberg PR](https://codeberg.org/ziglang/zig/pulls/30644), but lists [followup issue on github](https://github.com/ziglang/zig/issues/24601), which is closed with a [link to the currently open codeberg issue](https://codeberg.org/ziglang/zig/issues/30677).

What has happened here is that the migration from github to codeberg is “copy on write”. That is, if the issue needs further discussion, that happens on codeberg and the github issue is closed with a link to the codeberg issue. The route to the open issue is a bit circuitous, but that’s just a result of the issue tracker migration and project management over time.