getArgs -package:directory -package:gemini-exports -package:base -package:bnb-staking-csvs

getArgs for OsString. @since X.Y.Z

Computation getArgs returns a list of the program's command line arguments (not including the program name), as ByteStrings. Unlike getArgs, this function does no Unicode decoding of the arguments; you get the exact bytes that were passed to the program by the OS. To interpret the arguments as text, some Unicode decoding should be applied.

Computation getArgs returns a list of the program's command line arguments (not including the program name), as PosixStrings. Unlike getArgs, this function does no Unicode decoding of the arguments; you get the exact bytes that were passed to the program by the OS. To interpret the arguments as text, some Unicode decoding should be applied.

Lifted getArgs.

Based on GetCommandLineW. This behaves slightly different than getArgs. See the online documentation: https://learn.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-getcommandlinew

Based on GetCommandLineW. This behaves slightly different than getArgs. See the online documentation: https://learn.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-getcommandlinew

Computation getArgs returns a list of the program's command line arguments (not including the program name).

Lifted version of getArgs.

Returns a list of the program's command line arguments (not including the program name).

Get the arguments from the terminal command

Parse the CLI arguments with CmdArgs.

Convenience action: Initialize GLUT, returning the program name and any non-GLUT command line arguments.

Treat the String value, if any, of the given argument as a file handle and try to open it as requested. If not present, substitute the appropriate one of stdin or stdout as indicated by IOMode.

• Deprecated Return the String value, if any, of the given argument.

Like getArgs, but can also read arguments supplied via response files. For example, consider a program foo:

main :: IO ()
main = do
args <- getArgsWithResponseFiles
putStrLn (show args)

And a response file args.txt:

--one 1
--'two' 2
--"three" 3

Then the result of invoking foo with args.txt is:

> ./foo @args.txt
["--one","1","--two","2","--three","3"]

Inspect ahead of time what types will be searched in the Beans map.

>>> :{
let beans = fromDynList [toDyn @Int 5, toDyn False]
args = (,) <$> arg @Int <*> arg @Bool
in (getArgsReps args, runArgs (taste beans) args)
:}
(fromList [Int,Bool],(5,False))

Get the size of the data block used to specify arguments for this shader.

Gets args for the node.