in reply to Dealing with undefined captures in a substitution

If the sole purpose of a construct is to avoid a warning, I don't see why you shouldn't disable the warning explicitly. Only that warning, mind you, and in a small scope.
  • Comment on Re: Dealing with undefined captures in a substitution