# GraphRAG for LLM-Based Code Porting

**URL:** https://discourse.julialang.org/t/graphrag-for-llm-based-code-porting/134364
**Category:** Tooling
**Tags:** llm, rag, porting
**Created:** [December 4, 2025, 10:21pm UTC](https://discourse.julialang.org/t/graphrag-for-llm-based-code-porting/134364 "2025-12-04T22:21:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![andreeco](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@andreeco](https://discourse.julialang.org/u/andreeco)
#### Post date: [December 4, 2025, 10:21pm UTC](https://discourse.julialang.org/t/graphrag-for-llm-based-code-porting/134364/1 "2025-12-04T22:21:17Z")

</div>

In this [video](https://youtu.be/1VgptLwP588?si=1YgDhNzKtNK_fVGf) (from about 28:30 onwards), the speaker talks about GraphRAG for LLM-based code porting. He is from Microsoft and speaks about Rust adoption at the company.

The part on GraphRAG for code porting is only about five minutes to watch but has a nice example. It compares a prompt-based approach vs. code generation using GraphRAG. The code for GraphRAG is on [Microsoft’s GitHub](https://github.com/microsoft/graphrag).

What is your opinion of GraphRAG for code porting?