Sem: New primitive for code understanding – not LSPs, but entities on top of Git
Key takeaways
- Semantic understanding on top of Git.
- Everything works in any Git repo.
- │ ⊕ function validateToken [added] │ ∆ function authenticateUser [modified] │ ⊖ function legacyAuth [deleted] sem blame Who changed it?
Semantic understanding on top of Git. Diff, blame, impact, log. Functions, not lines.
Same commit. Different lens. Left: what git shows you. Right: what actually happened.
diff --git a/src/auth/login.ts b/src/auth/login.ts index 4a2b1c0..8f3d2e1 100644 --- a/src/auth/login.ts +++ b/src/auth/login.ts @@ -12,6 +12,18 @@ +export function validate Token(token: string) { + const decoded = jwt.verify(token, SECRET); + if (!decoded.exp || decoded.exp + throw new Token Expired Error(); + } + return decoded; +} + @@ -24,8 +36,10 @@ export async function authenticateUser( - const user = await db.findUser(email); - if (!user) return null; + const user = await db.findUser(email); + if (!user) throw new UserNotFoundError(); + await rateLimiter.check(email); @@ -45,12 +59,0 @@ -export function legacyAuth(user, pass) { - return db.query('SELECT * FROM users - WHERE email = ? AND password = ?', - [user, pass]); -} sem diff ┌─ src/auth/login.ts ──────────────── │ │ ⊕ function validateToken [added] │ ∆ function authenticateUser [modified] │ ⊖ function legacyAuth [deleted] │ └──────────────────────────────────── 3 entities changed across 1 file AI agents are 2.3x more accurate when given sem output vs raw line diffs. See the benchmark.