You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1\$\begingroup\$ You're mishandling special regexp characters like "." though \$\endgroup\$Stefan Reich– Stefan Reich2021-01-26 18:02:51 +00:00Commented Jan 26, 2021 at 18:02
- \$\begingroup\$ @StefanReich You're right, but the same applies to almost any other existing answer, though. But I've added a note to mention this in the answer (and golfed it by 3 bytes at the same time). \$\endgroup\$Kevin Cruijssen– Kevin Cruijssen2021-01-26 19:44:37 +00:00Commented Jan 26, 2021 at 19:44
- \$\begingroup\$ Come on... you're saying there is a bug in THIS? >> à øV << (the Japt program, whatever that is) \$\endgroup\$Stefan Reich– Stefan Reich2021-01-26 21:53:43 +00:00Commented Jan 26, 2021 at 21:53
- \$\begingroup\$ @StefanReich The golfing languages like Jelly, Japt, 05AB1E, etc. are probably fine, since most of them just use the powerset and check if the second input is in it. I was referring to the answers using regex like mine, like the accepted Perl answer; the Python answer of Eric; the Ruby answer; etc. All answers that use regex are similar as mine (add a ".*" after each characters, and check if it matches the second input) are most likely invalid if the inputs contain special regex characters. \$\endgroup\$Kevin Cruijssen– Kevin Cruijssen2021-01-26 22:07:09 +00:00Commented Jan 26, 2021 at 22:07
- \$\begingroup\$ I was just messing around :) \$\endgroup\$Stefan Reich– Stefan Reich2021-01-26 22:43:38 +00:00Commented Jan 26, 2021 at 22:43
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
\$\sin^2 \theta\$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. code-golf), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you