It seems there is a different raises behaviour for newTerminal()

Example

import terminal

proc test() {.raises:[IOError, ValueError].} =
  setBackgroundColor(stdout, bgRed)

test()

This will compile on Linux, but not on Windows. Error:

C:\Users\deme\repos\getterminalraises.nim(3, 22) templa

I'm opening this issue as more of a reminder than a one-time task.

It took me > 6 months to get familiar with the code base and I'm still weak in areas. Now this may say more about me than it does about the project, but I suspect the latter.

Adding header comments outlining the purpose of a file/class and how it's used by its dependents could go a long way toward easing onboarding for new co

So currently the doc for EReg.matched says this:

The index n corresponds to the n-th set of parentheses in the pattern
of this EReg. If no such sub-group exists, the result is unspecified.

But it's not immediately clear what "no such sub-group exists" means exactly. I assume it means that the group was not defined in the regex. But it's a bit confusing in case the group was define

If you make a new class C that inherits from a class B with a registered hy-repr function f-B, but don't register a function for C, then hy-repr on an instance of C will call f-B, which can be misleading: it looks like you have an instance of B when actually you have an instance of C. We should probably fall back on repr instead.

For example, pandas's Timestamp class inh

I've added a Rosetta Code page for Janet, but we still need some more examples. I've added an example for the 100 doors problem, but there are many more examples that can be added.

In the documentation https://github.com/decalage2/oletools/wiki/olevba, it says "MS Office files encrypted with a password are also supported, because VBA macro code is never encrypted, only the content of the document". This makes me think, for an encrypted office file, olevba can extract the macro with or without a password provided. However, this is not the case. olevba seems only extracts the

The explanation for why default arguments are a wart is pretty short and vague. Of course, users are welcome to disable that wart if they don't agree, but it would be nice to make a somewhat more compelling case for why default arguments should be avoided.

I think a simple example of a situation where default arguments causes an undesirable situation would make a big difference.

As also described in http://stackoverflow.com/questions/42059088/scala-logging-instantiating-logger-named-defined-in-logback-xml

having logger defined in logback.xml,

I can not instantiate it by

val goalProgressLogger = Logger("goal-progress-logger")

or

v

Parsing error on this sample: https://app.any.run/tasks/2be2b38f-4de2-4b48-8ae5-67bda9eecbaf

-------------------------------------------------------------------------------
PARSING VBA CODE:
INFO     parsed Sub z55e6df583 ([ByVal s2b7d47c629 as String]): 14 statement(s)
INFO     parsed Sub Document_Open (): 5 statement(s)
INFO     parsed Function tfaca84885f ([ByVal zd77f34558c as Varian

Macro tags are flags that serve as meta information #4. Turns out it may be a good thing to allow macro tags to have arguments:

macro ·name('MyMacro') { /* match */ } >> { /* expansion */ }

Blocks #15

The only place where this is currently done is FromStr: https://jeltef.github.io/derive_more/derive_more/from_str.html

Followup to #19; need to beef up example project to showcase a simple web application, where the front-end is based on Scala.js and the back-end on Scalatra or Akka HTTP (née Spray), sharing domain objects and Accord validators.

Currently, the crate has a fairly scattershot feature list in README.md, but no reference for each setting, its compatibility, and its function.

Questions

1. How should we explain to newcomers the value of the crate? Is a usage example best for that, or do we need to explain why people shouldn't make structs with all public fields?
2. Is serde.rs

It's not clear to me how nullValue and default (in decodeValue) are supposed to be used. E.g. it tripped me up that I can't pass null as default value, due to a null check.

Consider the example below:

bitflags! {
  pub struct MyFlags: u8 {
    #[doc = "abc"]
    const FLAG = 0b1000_0000;
  }
}

This results in an error no rules expected the token doc = "abc". This style of docs is needed to use bitflags within another macro that gets docs from the caller.

I wasn't sure how to get the server working... here's where I'm at:

Struggled with PowerShell (first time using PS_ISE):
When I opened a file in PS-ISE I didn't notice that I still needed to navigate to the working directory in order to load the other files.

Server started, what should be expected?
When I started the server, as expe