Skip to content

Commit

Permalink
Add matching-brackets
Browse files Browse the repository at this point in the history
  • Loading branch information
BNAndras committed Jun 25, 2024
1 parent e5e3885 commit 72511de
Show file tree
Hide file tree
Showing 8 changed files with 206 additions and 0 deletions.
8 changes: 8 additions & 0 deletions config.json
Original file line number Diff line number Diff line change
Expand Up @@ -596,6 +596,14 @@
"prerequisites": [],
"difficulty": 4
},
{
"slug": "matching-brackets",
"name": "Matching Brackets",
"uuid": "c206ca0e-4810-44c5-b519-9a0c660903a0",
"practices": [],
"prerequisites": [],
"difficulty": 5
},
{
"slug": "nucleotide-count",
"name": "Nucleotide Count",
Expand Down
5 changes: 5 additions & 0 deletions exercises/practice/matching-brackets/.docs/instructions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Instructions

Given a string containing brackets `[]`, braces `{}`, parentheses `()`, or any combination thereof, verify that any and all pairs are matched and nested correctly.
Any other characters should be ignored.
For example, `"{what is (42)}?"` is balanced and `"[text}"` is not.
8 changes: 8 additions & 0 deletions exercises/practice/matching-brackets/.docs/introduction.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Introduction

You're given the opportunity to write software for the Bracketeer™, an ancient but powerful mainframe.
The software that runs on it is written in a proprietary language.
Much of its syntax is familiar, but you notice _lots_ of brackets, braces and parentheses.
Despite the Bracketeer™ being powerful, it lacks flexibility.
If the source code has any unbalanced brackets, braces or parentheses, the Bracketeer™ crashes and must be rebooted.
To avoid such a scenario, you start writing code that can verify that brackets, braces, and parentheses are balanced before attempting to run it on the Bracketeer™.
18 changes: 18 additions & 0 deletions exercises/practice/matching-brackets/.meta/config.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
{
"authors": [
"BNAndras"
],
"files": {
"solution": [
"matching_brackets.vim"
],
"test": [
"matching_brackets.vader"
],
"example": [
".meta/example.vim"
]
},
"blurb": "Make sure the brackets and braces all match.",
"source": "Ginna Baker"
}
22 changes: 22 additions & 0 deletions exercises/practice/matching-brackets/.meta/example.vim
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
function! IsPaired(str) abort
let l:stack = []
let l:pairs = {'(': ')', '[': ']', '{': '}'}

for l:char in split(a:str, '\zs')
if has_key(l:pairs, l:char)
call add(l:stack, l:char)
elseif index(values(l:pairs), l:char) != -1
if empty(l:stack)
return 0
endif

let l:popped = remove(l:stack, -1)
if l:pairs[popped] !=# l:char
return 0
endif
endif
endfor

return empty(l:stack)
endfunction

70 changes: 70 additions & 0 deletions exercises/practice/matching-brackets/.meta/tests.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
# This is an auto-generated file.
#
# Regenerating this file via `configlet sync` will:
# - Recreate every `description` key/value pair
# - Recreate every `reimplements` key/value pair, where they exist in problem-specifications
# - Remove any `include = true` key/value pair (an omitted `include` key implies inclusion)
# - Preserve any other key/value pair
#
# As user-added comments (using the # character) will be removed when this file
# is regenerated, comments can be added via a `comment` key.

[81ec11da-38dd-442a-bcf9-3de7754609a5]
description = "paired square brackets"

[287f0167-ac60-4b64-8452-a0aa8f4e5238]
description = "empty string"

[6c3615a3-df01-4130-a731-8ef5f5d78dac]
description = "unpaired brackets"

[9d414171-9b98-4cac-a4e5-941039a97a77]
description = "wrong ordered brackets"

[f0f97c94-a149-4736-bc61-f2c5148ffb85]
description = "wrong closing bracket"

[754468e0-4696-4582-a30e-534d47d69756]
description = "paired with whitespace"

[ba84f6ee-8164-434a-9c3e-b02c7f8e8545]
description = "partially paired brackets"

[3c86c897-5ff3-4a2b-ad9b-47ac3a30651d]
description = "simple nested brackets"

[2d137f2c-a19e-4993-9830-83967a2d4726]
description = "several paired brackets"

[2e1f7b56-c137-4c92-9781-958638885a44]
description = "paired and nested brackets"

[84f6233b-e0f7-4077-8966-8085d295c19b]
description = "unopened closing brackets"

[9b18c67d-7595-4982-b2c5-4cb949745d49]
description = "unpaired and nested brackets"

[a0205e34-c2ac-49e6-a88a-899508d7d68e]
description = "paired and wrong nested brackets"

[1d5c093f-fc84-41fb-8c2a-e052f9581602]
description = "paired and wrong nested brackets but innermost are correct"

[ef47c21b-bcfd-4998-844c-7ad5daad90a8]
description = "paired and incomplete brackets"

[a4675a40-a8be-4fc2-bc47-2a282ce6edbe]
description = "too many closing brackets"

[a345a753-d889-4b7e-99ae-34ac85910d1a]
description = "early unexpected brackets"

[21f81d61-1608-465a-b850-baa44c5def83]
description = "early mismatched brackets"

[99255f93-261b-4435-a352-02bdecc9bdf2]
description = "math expression"

[8e357d79-f302-469a-8515-2561877256a1]
description = "complex latex expression"
62 changes: 62 additions & 0 deletions exercises/practice/matching-brackets/matching_brackets.vader
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@

Execute (paired square brackets):
Assert IsPaired("[]")

Execute (empty string):
Assert IsPaired("")

Execute (unpaired brackets):
Assert !IsPaired("[[")

Execute (wrong ordered brackets):
Assert !IsPaired("}{")

Execute (wrong closing bracket):
Assert !IsPaired("{]")

Execute (paired with whitespace):
Assert IsPaired("{ }")

Execute (partially paired brackets):
Assert !IsPaired("{[])")

Execute (simple nested brackets):
Assert IsPaired("{[]}")

Execute (several paired brackets):
Assert IsPaired("{}[]")

Execute (paired and nested brackets):
Assert IsPaired("([{}({}[])])")

Execute (unopened closing brackets):
Assert !IsPaired("{[)][]}")

Execute (unpaired and nested brackets):
Assert !IsPaired("([{])")

Execute (paired and wrong nested brackets):
Assert !IsPaired("[({]})")

Execute (paired and wrong nested brackets but innermost are correct):
Assert !IsPaired("[({}])")

Execute (paired and incomplete brackets):
Assert !IsPaired("{}[")

Execute (too many closing brackets):
Assert !IsPaired("[]]")

Execute (early unexpected brackets):
Assert !IsPaired(")()")

Execute (early mismatched brackets):
Assert !IsPaired("{)()")

Execute (math expression):
Assert IsPaired("(((185 + 223.85) * 15) - 543)/2")

Execute (complex latex expression):
let g:value = "\\left(\\begin{array}{cc} \\frac{1}{3} & x\\\\ \\mathrm{e}^{x} &... x^2 \\end{array}\\right)"
Assert IsPaired(g:value)

13 changes: 13 additions & 0 deletions exercises/practice/matching-brackets/matching_brackets.vim
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
" Given a string containing brackets, determine if the brackets are balanced.
"
" Example:
"
" :echo IsPaired("()[]{}")
" 1
" :echo IsPaired("[[")
" 0
"
function! IsPaired(str) abort
" your implemention goes here
endfunction

0 comments on commit 72511de

Please sign in to comment.